Just curious. If this is the first apache release, and cloudbridge was formerly in a different repo, why don't we just rip out the SOAP interface? That's a heck of a lot simpler than deprecating the first version of something.
-A On Aug 2, 2012 5:51 AM, "Chip Childers" <chip.child...@sungard.com> wrote: > On Wed, Aug 1, 2012 at 9:09 PM, Chiradeep Vittal > <chiradeep.vit...@citrix.com> wrote: > > It appears that the WSDL-based toolset is being deprecated by AWS [1]. > > > > Currently the EC2 API layer implements both the WSDL interface as well as > > the Query API. > > However the Query API is not well tested. > > Furthermore the implemented WSDL is of 2010-08 vintage. > > > > Does it make sense to likewise deprecate the WSDL interface in the EC2 > API > > compatibility module? > > +1 > > Chiradeep, would you be willing to make those changes? Or can someone > else step up? As David mentioned, beyond the logic that AWS is > deprecating that interface, it would eliminate a potential licensing > issue for us. > > > > > IMO we should focus on the Query API since everybody else seems to use > > this mode (and now even AWS is deprecating it). > > > > [1] > > > http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/CLTRG- > > common-args-api.html > > > > >
