Non-existent properties in POST are ignored for all the resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Low
|
Unassigned | ||
WSME |
Fix Released
|
Undecided
|
Stéphane Bisinger |
Bug Description
tempest.
tempest.
tempest.
tempest.
tempest.
tempest.
"description": "test1",
"links":
[{"href": "http://
{"href": "http://
"extra": {},
"created_at": "2014-02-
"updated_at": null,
"nodes": [{"href": "http://
{"href": "http://
"uuid": "b84fd02e-
Chassis created ignoring nonexistent property. But it should have been failed with 400 code.
Changed in ironic: | |
assignee: | nobody → Ramakrishnan G (rameshg87) |
Changed in ironic: | |
status: | Triaged → In Progress |
Changed in wsme: | |
assignee: | nobody → Stéphane Bisinger (kjir) |
status: | New → In Progress |
Changed in wsme: | |
milestone: | none → 0.8.0 |
status: | Fix Committed → Fix Released |
I cannot find anyway to handle this in ironic. wsme/pecan takes care of coverting the JSON data passed to the model object and ironic doesn't even get to see the non-existent properties passed. Shouldn't this be something that is configurable in wsme to throw HTTP 400 error code in case if non-existent fields are passed as POST request to the controller ?