-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
allow ipv4_address_count to be modifiable #5830
allow ipv4_address_count to be modifiable #5830
Conversation
See also: #5771 (I would suggest working together) |
@@ -525,6 +527,8 @@ resource "aws_launch_template" "test" { | |||
|
|||
network_interfaces { | |||
network_interface_id = "${aws_network_interface.test.id}" | |||
ipv4_address_count = 2 |
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.
We should probably split these out into their own acceptance tests and test configurations to make them more maintainable in the future. 👍
@bflad backed out of the ipv6 changes
|
@@ -211,12 +211,12 @@ Each `network_interfaces` block supports the following: | |||
* `delete_on_termination` - Whether the network interface should be destroyed on instance termination. | |||
* `description` - Description of the network interface. | |||
* `device_index` - The integer index of the network interface attachment. | |||
* `ipv6_addresses` - One or more specific IPv6 addresses from the IPv6 CIDR block range of your subnet. | |||
* `ipv6_addresses` - One or more specific IPv6 addresses from the IPv6 CIDR block range of your subnet. Conflicts with `ipv6_address_count` |
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.
This snuck in, but I think its fine to leave in as it'll be handled shortly.
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.
LGTM, thanks @kl4w! 🚀
10 tests passed (all tests)
--- PASS: TestAccAWSLaunchTemplate_nonBurstable (4.65s)
--- PASS: TestAccAWSLaunchTemplate_data (5.05s)
--- PASS: TestAccAWSLaunchTemplate_basic (5.16s)
--- PASS: TestAccAWSLaunchTemplate_importData (5.32s)
--- PASS: TestAccAWSLaunchTemplate_importBasic (5.68s)
--- PASS: TestAccAWSLaunchTemplate_networkInterface (8.01s)
--- PASS: TestAccAWSLaunchTemplate_tags (7.96s)
--- PASS: TestAccAWSLaunchTemplate_BlockDeviceMappings_EBS_DeleteOnTermination (37.76s)
--- PASS: TestAccAWSLaunchTemplate_BlockDeviceMappings_EBS (44.14s)
--- PASS: TestAccAWSLaunchTemplate_update (45.14s)
This has been released in version 1.36.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Fixes #5851
Changes proposed in this pull request:
Output from acceptance testing: