-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 Systems Manager resources: Add support for resource tags #8426
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While ~200 LOC may not look like too much, AFAIK we generally speaking prefer many smaller PRs (typically 1 per resource where possible) over few bigger ones.
I have left you some more comments inline, I hope you find these useful. 😉
Overall this looks very good for a first PR!
a978cca
to
781456a
Compare
Thanks for the very helpful review @radeksimko. I've rebased incorporating your suggestions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but another 👍 from Brian would be nice as I haven't properly worked on this repo for some time 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. Thank you for addressing this issue. I've left a few comments around acceptance testing and formatting but this is otherwise good to go. Please let me know if you need any help with the requested tests.
Note that "You can't add tags to or delete tags from an existing activation.". See https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_CreateActivation.html
Tag update after document creation is already supported.
Adding and updating tags on an SSM Parameter is already supported.
781456a
to
116426b
Compare
Thank you very much @nywilken. Review comments addressed mainly in rebased commits, with one new commit added for testing the tags |
… below acceptance test functions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kmoe this is good to go 🎉
I made one change before merging which was to move the testAccCheckAWSSSMActivationRecreated
definition after all of the acceptance test functions
Getting HTTP 400 errors when running 2.9.0 with existing SSM resources: 2019-05-07T19:29:23.139Z [DEBUG] plugin.terraform-provider-aws_v2.9.0_x4: 2019/05/07 19:29:23 [DEBUG] [aws-sdk-go] DEBUG: Response ssm/ListTagsForResource Details: AWS credential has full Administrator access, backing out to 2.8.0, no issue. |
Thanks for the comment @jonathanallen. Would you mind submitting a bug report in this repo with some more details and your Terraform configuration? In particular, it will be very useful to know whether your SSM Maintenance Window has tags defined. |
I was able to reproduce this outside of Terraform, I opened a support case with AWS and about 8 hours later the issue disappeared, still waiting for confirmation from AWS that they actually fixed something but this appears not to be an issue with this Terraform release. Thanks for your time. |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Fixes #7673
Changes proposed in this pull request:
Output from acceptance testing:
Note the one existing test fail, which will be fixed by #8324.