Closed jonathanq closed 11 years ago
I sent pull request https://github.com/espenak/awsfabrictasks/pull/9 that fixes the issue in a backward compatible way.
Great work! Just uploaded version 1.1.1 to pypi.
I also added a Contribute-section with your pull request #9 as example in the docs.
Happy to help! Please add a 1.1.1 tag when you have a moment. --r. On 29 May 2013, at 11:52, Espen Angell Kristiansen notifications@github.com wrote:
Great work! Just uploaded version 1.1.1 to pypi.
I also added a Contribute-section with your pull request #9 as example in the docs.
— Reply to this email directly or view it on GitHub.
Russ Ferriday -- Software and Systems Architect/Developer CEO Topia Systems Ltd. russf@topia.com -- +44 7429 518822 -- www.topia.com
Oups, I forgot git push --tags
:-) Should be pushed now.
We are using boto 2.6.0 and I discovered the ec2_list_instances call doesn't work anymore. Works fine with boto 2.5.2.
Looking at the changelog for boto 2.6.0 (https://github.com/boto/boto/compare/2.5.2...2.6.0) - specifically https://github.com/boto/boto/commits/develop/boto/ec2/instance.py it appears that the state attribute was removed and a new InstanceState class was created to hold the EC2 instance state. So "state" is no longer in the attributes. It is now _state. Placement was also changed and is now _placement (and an InstancePlacement class introduced).
in awsfabrictasks/ec2/api.py - print_ec2_instance:
If you change state -> _state and placement -> _placement - the code works, but you have to remove the:
Then you get:
Of course this won't work with older versions of boto - and doesn't really take advantage of the new data in boto 2.6.0 re: previous states. Anyway, I just wanted to report the issue. Not sure how best to handle the solution in a way to support both boto 2.5.2 and boto 2.6.0.