Skip to content
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

Fix --associate-public-ip-address option for EC2 run-instances #502

Merged
merged 3 commits into from
Nov 22, 2013
Merged

Fix --associate-public-ip-address option for EC2 run-instances #502

merged 3 commits into from
Nov 22, 2013

Conversation

garnaat
Copy link
Contributor

@garnaat garnaat commented Nov 22, 2013

If user specifies a --associate-public-ip-address option and provides a --subnet-id option, we have to move the subnet ID value into the NetworkInterfaces structure we have created or we get a client error from EC2. Fixes #501.

… a --subnet-id option, we have to move the subnet ID value into the NetworkInterfaces structure we have created or we get a client error from EC2. Fixes 501.
from awscli.arguments import CustomArgument

LOG = logging.getLogger(__name__)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOG doesn't appear to be used anywhere.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover testing kruft. Will remove.

@jamesls
Copy link
Member

jamesls commented Nov 22, 2013

Should we have a test that verifies that if you provide a --subnet-id without a --[no]-associate-public-ip-address that it does not get pulled into the NetworkInterfaces?

@garnaat
Copy link
Contributor Author

garnaat commented Nov 22, 2013

Good idea. I'll add that test.

@jamesls
Copy link
Member

jamesls commented Nov 22, 2013

:shipit: Looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--associate-public-ip-address option does not work
2 participants