-
Notifications
You must be signed in to change notification settings - Fork 50
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
expose with_public_ip var of metadata service #42
expose with_public_ip var of metadata service #42
Conversation
@@ -141,3 +141,9 @@ variable "extra_ui_static_env_vars" { | |||
default = {} | |||
description = "Additional environment variables for UI static app" | |||
} | |||
|
|||
variable "with_public_ip" { |
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.
@andreinechaev if you expose, you'll need to add to the README as well
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.
nit: now that I think of it we should probably make the description more descriptive too (I understand this PR copied it from the submodule, but still). Maybe something like "enable public IP assignment for the metadata service".
@Erin-Boehmer how did this work for you, since you added the option not to assign the IP in the first place in #37 ? I believe @andreinechaev ran into this issue with ECS not being able to pull images when it doesn't have IP address but runs in a public subnet. If it was a private subnet, I think it would be fine granted NAT gateway and Internet gateway are set up as usual. We should maybe add a note that you should either
I'm now trying to think what's the best way to communicate this to module users 🤔 Maybe add something in the description for the subnet setting too. |
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.
sorry for the delay, im going to include this into the next release
@oavdeev Agree, i ran into the same issue today. Therefore now the minimal example would not work, since the minimal example uses public subnets for the ECS. According to AWS, private subnets should have Maybe it would be good to add this into a quickstart guide or something. |
I'm thinking I'll add a note and maybe even remove the default in the next release, so the users have to read the note and make a conscious decision depending on their subnet setup |
No description provided.