As said in the meeting, this is an API behavior break that is not security related. We cannot have this bug fixed without microversions or API version rev.
I have marked the assosicated review with a -2 and a similar comment. I will remove the -2 once we have a way forward that is not an API contract break.
An idea floated was a strict query param that new clients can use to change behavior... there are ways to slice this, lets figure out a path forward and we can unblock it.
For the record, I like this being more explicit on non-supported params resulting in a 4xx.
As said in the meeting, this is an API behavior break that is not security related. We cannot have this bug fixed without microversions or API version rev.
See http:// specs.openstack .org/openstack/ api-wg/ guidelines/ evaluating_ api_changes. html#guidance
I have marked the assosicated review with a -2 and a similar comment. I will remove the -2 once we have a way forward that is not an API contract break.
An idea floated was a strict query param that new clients can use to change behavior... there are ways to slice this, lets figure out a path forward and we can unblock it.
For the record, I like this being more explicit on non-supported params resulting in a 4xx.