Fields should not be mandatory when updating
Bug #1274124 reported by
Nejc Saje
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| WSME |
New
|
Undecided
|
Unassigned | ||
Bug Description
Say you want to change a threshold of ceilometer alarm. You can't PUT {"threshold_rule": {"threshold": 70.0}}, because you get "Invalid input for field/attribute name. Value: 'None'. Mandatory field missing.".
Would it not be more user friendly to allow these sorts of PUTs? One way would be to add a flag to wsexpose that when set, the mandatory fields won't be enforced.
To post a comment you must log in.
