Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fly set-team fails silently when using -c with a bad config file #2904

Closed
jama22 opened this issue Dec 3, 2018 · 1 comment
Closed

Fly set-team fails silently when using -c with a bad config file #2904

jama22 opened this issue Dec 3, 2018 · 1 comment
Labels
accepted enhancement fly release/documented Documentation and release notes have been updated.
Milestone
v5.0.0

Comments

@jama22
Copy link
Member

jama22 commented Dec 3, 2018 •
edited

fly set-team fails silently when using -c with a bad config file.

For example, if I have a config file foo.txt:

asdf
asdf
asdf
asdf

and I do fly -t dev set-team -n this-is-wrong -c foobar.txt
I get...nothing. I expected a message at least telling me that there was "nothing to do" or "bad config file"
@jama22 jama22 changed the title Fly set-pipeline fails when using -c with a bad config file Fly set-pipeline fails silently when using -c with a bad config file Dec 3, 2018
@jama22 jama22 changed the title Fly set-pipeline fails silently when using -c with a bad config file Fly set-team fails silently when using -c with a bad config file Dec 3, 2018
mhuangpivotal pushed a commit that referenced this issue Dec 3, 2018
fly: show error message when parsing config file fails
fefdc10 
#2904

Signed-off-by: Mark Huang <mhuang@pivotal.io>
@jama22 jama22 closed this as completed Dec 10, 2018
@jama22
Copy link
Member Author

jama22 commented Dec 10, 2018

Now getting a "cannot unmarshal yml" error, so I'll accept

@vito vito added this to the v5.0.0 milestone Jan 10, 2019
@vito vito added the release/documented Documentation and release notes have been updated. label Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted enhancement fly release/documented Documentation and release notes have been updated.
Projects
None yet
Milestone
v5.0.0
Development

No branches or pull requests
2 participants
@vito @jama22