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.
>>>
>>> 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
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
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
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
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
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
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
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:
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
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 <<--
+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
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
>>
+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
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
15 matches
Mail list logo