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.

Sign up for GitHub

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

storagegateway commands having to do with volumes fail #1790

Closed
grimm26 opened this issue Feb 10, 2016 · 1 comment
Closed

storagegateway commands having to do with volumes fail #1790

grimm26 opened this issue Feb 10, 2016 · 1 comment
Labels
bug This issue is a bug.

Comments

@grimm26
Copy link

grimm26 commented Feb 10, 2016

It can't decide whether it wants --volume-arns or --volume-ar-ns

% aws --version                                                                                                                                                                                           
aws-cli/1.10.1 Python/2.7.10 Darwin/15.2.0 botocore/1.3.23
% aws storagegateway describe-stored-iscsi-volumes --volume-arns 'arn:aws:storagegateway:us-west-2:xxxxxxxxxx:gateway/sgw-xxxxxxxxxx/volume/vol-xxxxxxx'
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: argument --volume-ar-ns is required
% aws storagegateway describe-stored-iscsi-volumes --volume-ar-ns 'arn:aws:storagegateway:us-west-2:xxxxxxxxxx:gateway/sgw-xxxxxxx/volume/vol-xxxxxxx'                                                
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: argument --volume-arns is required
@jamesls
Copy link
Member

jamesls commented Feb 13, 2016

Confirmed bug, thanks for reporting.

@jamesls jamesls added the bug This issue is a bug. label Feb 13, 2016
@jamesls jamesls mentioned this issue Mar 1, 2016
Merged
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
@sriram-mv
fix: display no outputs if outputs are not defined. (aws#1790)
b352127 
Why is this change necessary?

* bug from previous PR which always looked for outputs in deployed
templates.

How does it address the issue?

* Explicitly check for outputs, before attempting to display them.
* Added extra tests to verify so that it does not cause regressions in
the future.

What side effects does this change have?

* None.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grimm26 @jamesls