required attribute validation is inconsistent
Bug #1465832 reported by
Ivar Lazzaro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
In Progress
|
Medium
|
Ivar Lazzaro | ||
Bug Description
This bug tracks adjustment to the required API attributes in GBP.
Today, some attributes are required even if they shouldn't, or could be easily replaced by a default. Some others, are both required AND with a default value (which doesn't make a REST sense, considering that the default value will always be there at the very least).
Also, our UTs add some attributes to the GBP resources creation that hide the REST API validation! This should be removed in order to make object creation in the UTs as similar to a user API call as possible
| Changed in group-based-policy: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Ivar Lazzaro (mmaleckk) |
| milestone: | none → kilo-gbp-4 |
| Changed in group-based-policy: | |
| status: | Confirmed → In Progress |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-4 → next |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on group-based-policy (master) | #1 |
To post a comment you must log in.
Change abandoned by Sumit Naiksatam (<email address hidden>) on branch: master
Review: https:/
Reason: Old patch, probably not needed, can be revived if needed.