-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Test that ec2 vpn client association works with multiple subnets #18199
Conversation
Amazon API doesn't return the correct results when using "AssociationIds" but works correctly when using a filter for the same thing
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.
Otherwise looks good 🚀
Output from acceptance testing in AWS Commercial:
--- PASS: TestAccAwsEc2ClientVpn_serial (0.98s)
--- PASS: TestAccAwsEc2ClientVpn_serial/NetworkAssociation_securityGroups (682.09s)
--- PASS: TestAccAwsEc2ClientVpn_serial/NetworkAssociation_basic (732.78s)
--- PASS: TestAccAwsEc2ClientVpn_serial/NetworkAssociation_disappears (740.80s)
--- PASS: TestAccAwsEc2ClientVpn_serial/NetworkAssociation_multipleSubnets (955.03s)
Tests fail (as expected) in AWS GovCloud (US) as the functionality is not supported in that partition.
Co-authored-by: Brian Flad <bflad417@gmail.com>
This has been released in version 3.33.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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! |
This originally included a fix for a problem that was occurring on the AWS side. They have since fixed the issue, so I have removed the changes that were required to work around the problem. The test should still be included to confirm the issue is resolved, and is not broken again in the future.
Community Note
Closes #11586
Output from acceptance testing: