You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
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
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.
Terraform CLI and Terraform AWS Cloud Control Provider Version
#2153 resolves this as the schema was available as of this week to be picked up for tags. You should be able to use tags on the VPC endpoint with v1.25.0 of the provider. Closing this issue based on the updated schema. Please re-open if you notice further issues with this.
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The CloudFormation resource AWS::EC2::VPCEndpoint supports tags, so the AWSCC resource should too.
Actual Behavior
Error: An argument named "tags" is not expected here.
The text was updated successfully, but these errors were encountered: