-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boto3 conversion #32
Boto3 conversion #32
Conversation
fix detecting associated addresses fix two spelling errors
Just a quick bump on this -- if you'd prefer to stick with boto2, given the problems from the last release, I understand, but we will want to continue work in our fork to add features. |
@sebdah It appears that we also ran into reassociation bug. Because the default has changed, it's impossible to send valid request with old boto. In order to fix this, a client change to boto3 is required. Would you be willing to look into this? |
I'm really swamped with dealing with Covid-19 stuff at work, if someone could review the code and give this branch a go I'd be happy to merge, package and release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a python expert, but the code looks okay to me :)
Tested this branch on EC2 with the following:
pip install ec2_metadata git+https://github.com/pmkane/aws-ec2-assign-elastic-ip.git@boto3_conversion
, worked well.
@pmkane Could you update to master?
Sure. I’ll do it this weekend.
On Fri, Apr 3, 2020 at 1:59 PM Przemysław Elias ***@***.***> wrote:
***@***.**** approved this pull request.
I'm not a python expert, but the code looks okay to me :)
Tested this branch on EC2 with the following:
pip install ec2_metadata git+
***@***.***_conversion,
worked well.
@pmkane <https://github.com/pmkane> Could you update to master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#32 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL5KV5A7KMI5LQUJWHMJD3RKYWX3ANCNFSM4GYWZT2A>
.
--
Patrick Michael Kane
<[email protected]>
|
Done. |
Awesome, thanks guys. I'll get to this a little later today. |
Thanks for the help here @pmkane and @przemyslaw-elias. I have released version 0.10.0 now. |
Guys, it looks like the merge to master didn't go as planned. Before that it's been working properly, but now it's giving an error:
@pmkane in your PR you changed Moreover, I don't know whats wrong, but I had to manually run |
Hmm, yes, there is a new dependency added. It must be added to the list of dependencies. Also it seems like the boto dependency should be bumped. I'll prepare a bugfix PR shortly. |
Ugh, sorry -- I clearly rushed the merge. I am happy to submit a PR to clean up my own mess. Will do so, unless @sebdah has already gotten there. |
Looks like you did, thank you @sebdah. |
Hi there:
This a new PR to convert aws-ec2-assign-elastic-ip to use boto3, instead of boto.
Because boto3 still doesn't have get_instance_metadata() equivalent, it adds ec2-metadata as a requirement.
The only functional change in this PR is that AllowReassociation is always False, whereas in the current boto implementation, whether it is True or False depends on the date that your EC2 environment was created. See #24 for more details.
I've tested the use cases that broke in #28 or #29 and they both work correctly in this branch.