OSC operations that have optional params don't raise an error when no options are passed
Bug #2032984 reported by
Goutham Pacha Ravi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-manilaclient |
In Progress
|
Low
|
Solomon Barine Akpuru |
Bug Description
This is a UX improvement RFE.
When using the OSC CLI, when a command has optional parameters, not providing any of these options doesn't currently raise any errors.
For example:
Here, if you use:
$ openstack share security service set mysecservice
i.e, you specify the pos arg in this case (Security service name or ID) but not any of the optional args, the command does nothing. This pattern exists elsewhere too.
It'd be nice for the CLI to suggest that one or more of the options are necessary to have an effect; perhaps as a warning log?
summary: |
- OSC operations that have optional components don't raise an error when - no options are passed + OSC operations that have optional params don't raise an error when no + options are passed |
Changed in python-manilaclient: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in python-manilaclient: | |
assignee: | nobody → Solomon Barine Akpuru (solly47) |
To post a comment you must log in.
Hi Goutham, could you assign this bug to me?