jclouds / legacy-jclouds-cli

https://jclouds.apache.org
Apache License 2.0
17 stars 5 forks source link

jclouds-cli does not support --identity and --credential arguments #24

Closed gaul closed 11 years ago

gaul commented 11 years ago

The help string suggests using these but jclouds-karaf does not accept them. I also see no mention of them in commands/src/main/resources/OSGI-INF/blueprint/jclouds-commands.xml

iocanel commented 11 years ago

Both jclouds-karaf and jclouds-cli support these options:

For example: ./bin/jclouds node list --identity myidentity --credential mycredential --provider aws-ec2 works fine.

Also the options of a command do not have to be listed inside the blueprint descriptor. They are defined inside the class using annotations.

My guess is that the options were not put in the right order.

demobox commented 11 years ago

They are defined inside the class using annotations.

Do you mean something like BlobStoreCommandWithOptions?

demobox commented 11 years ago

but jclouds-karaf does not accept them

@andrewgaul Could you give an example of the test case you tried that failed? Thanks!

iocanel commented 11 years ago

@demobox, exactly!

gaul commented 11 years ago

Sorry, user error. jclouds-cli requires arguments in a specific order:

jclouds category action --options arguments

This confused me; I had tried these permutations as well:

jclouds category action arguments --options jclouds --options category action arguments

demobox commented 11 years ago

Perhaps an explicit comment somewhere near Using the CLI such as "arguments are required in specific order"..?