-deploy API without endpoint defined in terraform, not vpce is added to API
-explicitly define vpce in terraform, endpoint is added
-remove vpce in terraform, endpoint remains
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.4.6
AWS Provider Version
4.67.0
Affected Resource(s)
aws_api_gateway_rest_api
Expected Behavior
I'm attempting to deploy a Private API with a VPC Endpoint configuration using an openapi spec containing the following block of yaml in the API spec:
and a corresponding block of terraform:
the module is called like this:
with
var.vpce
being provided as a string in the TFVARS file likevpce = "vpce-xxxxx"
Looking at the documentation, I think this should deploy a Private API with the specified VPC Endpoint in the Endpoint Configuration.
Actual Behavior
A Private API is deployed, but the VPC Endpoint is not listed in the configuration. If you deploy the endpoint via terrafrom like
this works, and if you remove this explicit definition and apply, terraform reports 'No changes' and the endpoint remains.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
https://gist.github.com/jamiegosling/f2e4c655cb47c5ddcc23e22fe625bc2d
Steps to Reproduce
-deploy API without endpoint defined in terraform, not vpce is added to API -explicitly define vpce in terraform, endpoint is added -remove vpce in terraform, endpoint remains
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None