Re: [openstack-dev] [api] Minor changes to API

2015-04-21 Thread Everett Toews
On Apr 20, 2015, at 2:19 PM, Douglas Mendizabal mailto:douglas.mendiza...@rackspace.com>> wrote: Hi openstack-dev@ I was wondering if the API Working Group had an opinion on how to deal with minor changes to the api? For example, what if you wanted to add a new attribute to a JSON response?

Re: [openstack-dev] [api] Minor changes to API

2015-04-21 Thread Everett Toews
On Apr 20, 2015, at 7:07 PM, Ian Wells mailto:ijw.ubu...@cack.org.uk>> wrote: On 20 April 2015 at 15:23, Matthew Treinish mailto:mtrein...@kortar.org>> wrote: On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: > It would be nice to have a consistent policy here; it would make future > de

Re: [openstack-dev] [api] Minor changes to API

2015-04-21 Thread Ian Wells
On 20 April 2015 at 17:52, David Kranz wrote: > On 04/20/2015 08:07 PM, Ian Wells wrote: > > Whatever your preference might be, I think it's best we lose the > ambiguity. And perhaps advertise that page a little more widely, actually > - I hadn't come across it in my travels. And perhaps impro

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread David Kranz
On 04/20/2015 08:07 PM, Ian Wells wrote: On 20 April 2015 at 15:23, Matthew Treinish > wrote: On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: > It would be nice to have a consistent policy here; it would make future > decision making easier

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread Ian Wells
On 20 April 2015 at 15:23, Matthew Treinish wrote: > On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: > > It would be nice to have a consistent policy here; it would make future > > decision making easier and it would make it easier to write specs if we > > knew what was expected and th

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread Matthew Treinish
On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: > On 20 April 2015 at 13:02, Kevin L. Mitchell > wrote: > > > On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote: > > > > However, minor changes like that could still possibly break clients > > that are not > > > > expecting them. Fo

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread Ian Wells
On 20 April 2015 at 13:02, Kevin L. Mitchell wrote: > On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote: > > > However, minor changes like that could still possibly break clients > that are not > > > expecting them. For example, a client that uses the json response as > arguments > > > to a

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread Kevin L. Mitchell
On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote: > > However, minor changes like that could still possibly break clients that > > are not > > expecting them. For example, a client that uses the json response as > > arguments > > to a method via **kwargs would start seeing TypeErrors for u

Re: [openstack-dev] [api] Minor changes to API

2015-04-20 Thread Chris Friesen
On 04/20/2015 01:19 PM, Douglas Mendizabal wrote: Hi openstack-dev@ I was wondering if the API Working Group had an opinion on how to deal with minor changes to the api? For example, what if you wanted to add a new attribute to a JSON response? I would think that a minor change like that could