"server create" accepts undocumented --key argument
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
New
|
Undecided
|
Praveen N |
Bug Description
Some users are reporting confusion that setting the keypair with --key in "openstack server create" works, even though it should result an argument error according to the help documentation:
$ openstack help server create
usage: openstack server create [-h] [-f {json,shell,
Despite this using the following works and sets the ke ycorrectly:
$ openstack server create --image cirros --flavor m1.tiny --key test cirrostest
From my understanding, the source of confusion is that when debugging an issue with server creation, the user notices that --key wasn't an option and thought this was the source of the problem, when it was actually fine. It sounds like either adding --key as a documented option in the --help, or removing the option altogether would help to alleviate the confusion.
Changed in python-openstackclient: | |
assignee: | nobody → Praveen N (praveenn) |
This seems to be valid.
Also noticed, this holds similar with "openstack server create --security" instead of --security-group parameter.