image set v2 uses visibility option instead of public and private
Bug #1476772 reported by
Terry Howe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Invalid
|
Undecided
|
Sean Perry |
Bug Description
The image set command for v2 uses visibility option instead of --public|--private
Also investigate --protected|
Add notes to barkward-
Changed in python-openstackclient: | |
assignee: | nobody → Sean Perry (sean-perry-a) |
status: | New → In Progress |
To post a comment you must log in.
I do not mind converting --visibility to public/private. Consistency with others does have value.
But --unprotected is bad UX in my opinion. If --protected is not provided the value is False. --unprotected performs no useful function. You are always 'unprotected' unless you use --protected. Why provide a parameter that never needs to be used?