-
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
Provider accesses DescribeVpcClassicLink API calls when ClassicLink is disabled #28089
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Relates #23625. |
This functionality has been released in v5.0.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Hi, this issue is the same as #15107 . Could not re-open that issue.
The details goes as follows: I am trying to create a EKS cluster and it works well with the ap-south-1 region but facing this problem when i switch the region to ap-southeast-1 or any other one. This happens although my account does not have classic link enabled or even if I mention the enable_classic_link as false.
Terraform CLI and Terraform AWS Provider Version
Terraform v1.3.5
Affected Resource(s)
aws_vpc
Terraform Configuration Files
Debug Output:
Panic Output
N/A
Expected Behavior
It should create a EKS cluster in the specified region ( eg: ap-southeast-1 and us-east-1 -- i have tried)
Actual Behavior
Terraform calls out to DescribeVpcClassicLink when creating a VPC that has ClassicLink disabled
References
No response
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: