<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>It sounds like there isn't any major objection to moving forward
with a fix and getting this into Pike. I would be inclined to say
the discussion here has elevated that priority since missing Pike
would expose the 204 -> 403 in an official release.<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/07/2017 03:54 AM, Chris Dent
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1708070948140.95755@cdent-m01.vmware.com">On
Fri, 4 Aug 2017, Lance Bragstad wrote:
<br>
<blockquote type="cite">On 08/04/2017 03:45 PM, Kristi Nikolla
wrote:
<br>
<blockquote type="cite">Therefore the call which now returns a
403 in master, returned a 2xx in
<br>
Ocata. So we would be fixing something which is broken on
master rather
<br>
than changing a ‘contract’.
<br>
</blockquote>
<br>
Good call - with that in mind I would be inclined to say we
should fix
<br>
the issue in Pike that way we keep the 204 -> 204 behavior
the same
<br>
across releases. But I'll defer to someone from the API WG just
to make
<br>
sure.
<br>
</blockquote>
<br>
I think that's fair. Given that you're not doing microversions and
<br>
you aren't inclined to commit to CD, it's a pragmatic solution to
<br>
mis-functionality that was introduced between code releases.
<br>
<br>
It also sounds like an edge case where it's very unlikely that
<br>
there's extant client code that is relying on that 403 to make
<br>
decisions on next steps.
<br>
<br>
The interop guideline is intentionally very strict and detailed,
to
<br>
make it clear how much you need to think about to really do it
well,
<br>
but in many cases should be considered as a tool for evaluating
the
<br>
extent of the damage a change might cause, not the law.
<br>
<br>
Especially if you haven't got microversions available.
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>