-
Notifications
You must be signed in to change notification settings - Fork 11
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
Refactor and add new services #10
base: master
Are you sure you want to change the base?
Conversation
Will check the PR and merge. Thanks. |
@ilayanambi86 Any update on this PR? |
Hi, didn't get time to check. Will try this weekend. Thanks for your support. |
Would also love to see this! Added a very specific resource I'm looking into, namely CloudWatch Log Groups. |
Would be nice to see this merged and get tags on our SNS topics. |
@m-radzikowski m-radzikowski can resolve the conflicts. I will create a beta version for this to validate the change. |
@ilayanambi86 updated. I tested it, for some reason HTTP API Gateway tags were not added, despite them being defined in the CloudFormation template. Take a look if you have a minute or let me know, I will investigate it further. |
Not to suggest that additional requests should block merging at all, but I just wondered if there's a reason to omit the CloudFormation stack itself - is it not possible? |
Also, why have the hard-coded list at all? Couldn't we just try it for each resource - no check if it's a supported one - and if the error is 'no such operation TagResource' or whatever, just ignore it and continue? |
This project seems severely outdated, so had to roll a new tagging plugin with more features and resource type support. |
Hey @ilayanambi86
the trouble with CloudFormation tags not being propagated is real and I like the approach you took with this plugin!
I needed it to support more services. I refactored the code to enable it. The changes I made:
Please let me know what do you think.