-
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
r/aws_subnet: Resource-based naming is not available in the ap-southeast-3
region
#22531
Conversation
…Pacific (Jakarta) Region.
…ilable in the AWS Asia Pacific (Jakarta) Region.
5885d18
to
f0a18dc
Compare
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.
Looks good! 🎉
--- PASS: TestAccEC2Subnet_basic (23.81s)
… not available in the AWS Asia Pacific (Jakarta) Region." This reverts commit 3cbedba.
Reverting the acceptance test changes as we don't experience any failures during usual testing. |
This functionality has been released in v3.72.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. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #22498.
Previously:
Now
Also addresses failing CI test:
Output from acceptance testing:
ap-southeast-3
us-west-2