boto_vpc.subnet_present add auto_assign_ipv4 and auto_assign_ipv6 #67313
Replies: 9 comments
-
@twellspring sounds like a solid idea to add this to that state. Thanks will approve as a feature request. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Beta Was this translation helpful? Give feedback.
-
Without this feature, a Salt user must manually configure Auto-assign IPv4 (Enable auto-assign public IPv4 address) between the creation of the subnet and the creation of any public instances. Having a manual step in the middle of Infrastructure as Code is a bummer. The only automated option is to use an Elastic IP address. The number of Elastic IP addresses allowed by AWS is limited. |
Beta Was this translation helpful? Give feedback.
-
will re-open for ya. This is not currently assigned out to anyone so please feel free to submit a PR |
Beta Was this translation helpful? Give feedback.
-
Thank you for updating this issue. It is no longer marked as stale. |
Beta Was this translation helpful? Give feedback.
-
Thank you for updating this issue. It is no longer marked as stale. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Beta Was this translation helpful? Give feedback.
-
please keep this ticket open |
Beta Was this translation helpful? Give feedback.
-
Thank you for updating this issue. It is no longer marked as stale. |
Beta Was this translation helpful? Give feedback.
-
Description of Issue/Question
Request to add auto_assign_ipv4 and auto_assign_ipv6 to the boto_vpc.subnet_present state.
Without this value, all subnets created with boto_vpc.subnet_present will have the default of no for both auto assigned values, and all servers later created with either boto_ec2 or salt-cloud will not have a public IP unless it is explicitly specified.
In cloud.profiles that means:
I tested the cloud.profiles network_interfaces option without an AssociatePublicIpAddress value and it will use the subnet default value, so adding the auto_assign values to boto_vpc.subnet_present would allow public IPs to be managed without an explicit in salt-cloud.
My workflow for managing AWS with Saltstack is to use boto states to create everything besides servers and use salt-cloud to create all servers. I can put some logic into my salt-create script to add the
AssociatePublicIpAddress
to the cloud.profile based on subnet name ( enable in web subnets, disable in app subnets ). But being able to set the values on the subnet and then let salt-cloud use those defaults would be cleaner.Beta Was this translation helpful? Give feedback.
All reactions