This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allowing users to choose whether their instances should get a public IP address or not. Defaulting to "no".
What I did
Supporting
x-aws-assign_public_ip
in the service level.If not present / set to a falsy value, the service should not get a public IP address.
If set to a truthy value, the current behavior exists (set by the provider's capability).
I'm not touching the EC2 section as it seems a bit messed up anyway, and I suspect it's not covered by tests.
Related issue
#2213
Created new "slightly complex" test to cover my change. I intend to reuse it later as well.
(not mandatory) A picture of a cute animal, if possible in relation with what you did
Called Dubi. A friendly street cat.