-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: unable to set "name" argument in aws_api_gateway_vpc_link when using as a module. #32101
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @vyshnavlal 👋 Thank you for taking the time to raise this! In your In order to correctly call the
The updated configuration in module "vpclink" {
source = "./modules/vpc_link"
vpclink_name = var.vpclink_name
target_arn = var.target_arn
} |
Since we haven't heard back, I'm going to close this issue. If you're still having trouble, please feel free to open a new issue, referencing this one for context as needed. |
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. |
Terraform Core Version
1.5.0
AWS Provider Version
4.67.0
Affected Resource(s)
aws_api_gateway_vpc_link
Expected Behavior
It should support "name" argument as per the documentaion.
Actual Behavior
Getting the error: │ An argument named "name" is not expected here.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
-> modules/vpc_link/main.tf
-> modules/vpc_link/variables.tf
->modules/vpc_link/outputs.tf
->main.tf
->variables.tf
->terraform.tfvars
->outputs.tf
Steps to Reproduce
terraform validate
Debug Output
Panic Output
No response
Important Factoids
There are no errors when creating the resource "aws_api_gateway_vpc_link" without using a module. The documentaion includes
name = "example"
in the example usage.References
Adding the respective documentation
No other source found in internet regarding the "name" behavior issue.
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: