Re: [DISCUSS] API versioning

2017-06-06 Thread Ron Wheeler
he.org <mailto:dev@cloudstack.apache.org> Subject: Re: [DISCUSS] API versioning +1 Good idea, though bear in mind there are 500+ APIs with no modern-RESTful-standardization, a lot of work. Regards.

Re: [DISCUSS] API versioning

2017-06-06 Thread Tutkowski, Mike
>>> >>> From: Rohit Yadav <rohit.ya...@shapeblue.com> >>> Sent: Monday, June 5, 2017 4:04 AM >>> To: dev@cloudstack.apache.org >>> Subject: Re: [DISCUSS] API versioning >>> >>> +1 Good i

Re: [DISCUSS] API versioning

2017-06-06 Thread Syed Ahmed
have a lot of cleanup to do :-) It >>> certainly makes it a lot easier though when you're not breaking >>> compatibility with existing code. >>> >>> >>> From: Rohit Yadav <rohit.ya...@shapeblue.com> >>> Se

Re: [DISCUSS] API versioning

2017-06-05 Thread Ron Wheeler
g code. From: Rohit Yadav <rohit.ya...@shapeblue.com> Sent: Monday, June 5, 2017 4:04 AM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] API versioning +1 Good idea, though bear in mind there are 500+ APIs with no modern-RESTful-standardization, a lot of wor

Re: [DISCUSS] API versioning

2017-06-05 Thread Ron Wheeler
com> Sent: Monday, June 5, 2017 4:04 AM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] API versioning +1 Good idea, though bear in mind there are 500+ APIs with no modern-RESTful-standardization, a lot of work. Regards. From: Nitin Kumar Maharana <n

Re: [DISCUSS] API versioning

2017-06-05 Thread Daan Hoogland
o do :-) It > > certainly makes it a lot easier though when you're not breaking > > compatibility with existing code. > > > > > > From: Rohit Yadav <rohit.ya...@shapeblue.com> > > Sent: Monday

Re: [DISCUSS] API versioning

2017-06-05 Thread Syed Ahmed
lot of cleanup to do :-) It > > certainly makes it a lot easier though when you're not breaking > > compatibility with existing code. > > > > > > From: Rohit Yadav <rohit.ya...@shapeblue.com> > > Sent: Monday, June 5, 2017 4:04

Re: [DISCUSS] API versioning

2017-06-05 Thread Rafael Weingärtner
nday, June 5, 2017 4:04 AM > To: dev@cloudstack.apache.org > Subject: Re: [DISCUSS] API versioning > > +1 Good idea, though bear in mind there are 500+ APIs with no > modern-RESTful-standardization, a lot of work. > > > Regards. > > > From: Nitin Kum

Re: [DISCUSS] API versioning

2017-06-05 Thread Simon Weller
o: dev@cloudstack.apache.org Subject: Re: [DISCUSS] API versioning +1 Good idea, though bear in mind there are 500+ APIs with no modern-RESTful-standardization, a lot of work. Regards. From: Nitin Kumar Maharana <nitinkumar.mahar...@accelerite.com> Sent:

Re: [DISCUSS] API versioning

2017-06-05 Thread Rohit Yadav
ISCUSS] API versioning This looks good. +1 rohit.ya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > On 04-Jun-2017, at 2:34 PM, Rene Moser <m...@renemoser.net> wrote: > > Hi > > I recently developed ansible modules fo

Re: [DISCUSS] API versioning

2017-06-05 Thread Nitin Kumar Maharana
This looks good. +1 > On 04-Jun-2017, at 2:34 PM, Rene Moser wrote: > > Hi > > I recently developed ansible modules for the ACL API and ... found this > has a really inconsistent API naming. E.g. > > createNetworkACL <<-- this creates an ACL rule > createNetworkACLList <<--

Re: [DISCUSS] API versioning

2017-06-05 Thread Boris Stoyanov
+1 boris.stoya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > On Jun 4, 2017, at 7:15 PM, Tutkowski, Mike wrote: > > This sounds like a good idea to me. > >> On Jun 4, 2017, at 8:24 AM, Will Stevens

Re: [DISCUSS] API versioning

2017-06-04 Thread Tutkowski, Mike
This sounds like a good idea to me. > On Jun 4, 2017, at 8:24 AM, Will Stevens wrote: > > +1. I like it. > >> On Jun 4, 2017 5:04 AM, "Rene Moser" wrote: >> >> Hi >> >> I recently developed ansible modules for the ACL API and ... found this >>

Re: [DISCUSS] API versioning

2017-06-04 Thread Will Stevens
+1. I like it. On Jun 4, 2017 5:04 AM, "Rene Moser" wrote: > Hi > > I recently developed ansible modules for the ACL API and ... found this > has a really inconsistent API naming. E.g. > > createNetworkACL <<-- this creates an ACL rule > createNetworkACLList <<-- this create

[DISCUSS] API versioning

2017-06-04 Thread Rene Moser
Hi I recently developed ansible modules for the ACL API and ... found this has a really inconsistent API naming. E.g. createNetworkACL <<-- this creates an ACL rule createNetworkACLList <<-- this create the ACL updateNetworkACLItem <<-- this updates an ACL rule updateNetworkACLList <<-- this