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

Raise exception when bad output format is given #716

Merged
merged 1 commit into from
Mar 21, 2014

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Mar 21, 2014

While argparse handles the case where it's specified as an arugment, we need
to validate the case when output is specified as an env var and a config var.

While argparse handles the case where it's specified as an arugment,
we need to validate the case when output is specified as an env var
and a config var.
@jamesls
Copy link
Member Author

jamesls commented Mar 21, 2014

Forgot to link issue number, this fixes #600

@danielgtaylor
Copy link
Contributor

LGTM, the exception is much nicer than just returning None. 🚢-it!

@jamesls jamesls merged commit c4ce951 into aws:develop Mar 21, 2014
@jamesls jamesls deleted the bad-output-type branch June 23, 2014 18:27
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this pull request Feb 12, 2022
Git maintenance: get across commits from the 0.6.0 release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants