Why are they even changing? Once we publish an API, we should stick with it... otherwise we have to bump to version 5.0.0 for our next feature release.
On Tue, Dec 3, 2013 at 10:01 AM, Suresh Sadhu <suresh.sa...@citrix.com> wrote: > Rajani, > > Is there any specific reason for removing existing API's.why don't we show > them as deprecated api but still it should work right > > Regards > Sadhu > > > -----Original Message----- > From: Chip Childers [mailto:chip.child...@gmail.com] > Sent: 03 December 2013 18:17 > To: dev@cloudstack.apache.org; Rajani Karuturi > Subject: Re: Ldap APIs > > So we are breaking API compatibility? > >> On Dec 3, 2013, at 7:42 AM, Rajani Karuturi <rajani.karut...@citrix.com> >> wrote: >> >> Hi Gaurav, >> >> addLdapConfiguration and deleteLdapConfiguration are the new commands. >> >> more information is available @ >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provi >> sioning >> >> -- >> Thanks, >> Rajani >> >> >> ----Original Message----- >> >> Reply-to: <dev@cloudstack.apache.org> >> To: dev@cloudstack.apache.org >> <dev@cloudstack.apache.org<mailto:%22...@cloudstack.apache.org%22%20%3 >> c...@cloudstack.apache.org%3e>> >> Subject: Ldap APIs >> Date: Tue, 3 Dec 2013 17:54:16 +0530 >> >> >> >> Hi all, >> >> When ldapConfig and ldapRemove APIs are fired, it shows error as >> "Unknown API command". >> >> These APIs are listed under 4.2 admin API guide and we test cases to >> test them. Are these APIs removed recently? I am testing against 4.3. >> >> Regards, >> Gaurav >>
