-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Supporting resource-based hostnames #762
Comments
hi @m1keil - this should be addressed in the next version which is under development here https://github.com/clowdhaus/terraform-aws-vpc-v4/tree/main/modules/subnets |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
hi, I was looking for this but couldn't see it has been added to the vpc module, or has it? |
We should re-open this. This feature has also been requested in issue #840 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS?
AWS allows changing the hostname scheme from the legacy ip-based naming to resource-based naming. More info available here
On the provider side this all comes down to the following control knobs on the
aws_subnet
resource:Describe the solution you'd like.
It can be simply done by exposing the three variables on the top level. I'm not sure if it makes sense to make this configurable on a per subnet base or not.
Additional context
RBN (resource-based naming) was introduced as part of the IPv6-only subnets announcement
The text was updated successfully, but these errors were encountered: