Skip to content
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

AWS::EC2::VPCEndpoint-Tags support missing #202

Closed
trav-c opened this issue Oct 4, 2019 · 3 comments
Closed

AWS::EC2::VPCEndpoint-Tags support missing #202

trav-c opened this issue Oct 4, 2019 · 3 comments

Comments

@trav-c
Copy link

trav-c commented Oct 4, 2019

1. Title

AWS::EC2::VPCEndpoint-Tags

2. Scope of request

AWS::EC2::VPCEndpoint does not support tagging, however VPCEndpoints can be tagged using the EC2 CreateTags and DeleteTags API, the VPCEndpoint CloudFormation resource should support management of these tags in the same manner as some other EC2 resources already support.

3. Expected behavior

Tags specified on the resource in the CloudFormation template should be created / updated / deleted on the actual EC2 resource

4. Suggest specific test cases

  1. Set a Name Tag on the VPC Endpoint in the CloudFormation template and ensure it's value is visible when making a DescribeTags API call for the VPC Endpoint resource
  2. Update the Name Tag on the VPC Endpoint in the CloudFormation template and ensure it's new value is reflected when making a DescribeTags API call for the VPC Endpoint resource
  3. Delete the Name Tag on the VPC Endpoint in the CloudFormation template and ensure it's new value is reflected when making a DescribeTags API call for the VPC Endpoint resource

5. Helpful Links to speed up research and evaluation

EC2 Resource Tagging API Methods

AWS::EC2::Instance Tags attribute - it would be good if the behaviour and syntax was consistent with this

6. Category

  • Compute
  • Networking & Content
@TheDanBlanco
Copy link

looks like a duplicate of #196 - if this isn't the case please re-open this issue!

@ajoga
Copy link

ajoga commented Oct 15, 2019

@TheDanBlanco Could I suggest you to re-open this one which is way more detailed than #196 ? This one is scoping way more the work expected, and from my perspective I can see that it isn't including in its scope what I'm looking for, therefore I'm going to open another request... That you could also see as a duplicate of #196. Thanks.

@davidgatti
Copy link

2024...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants