-
Notifications
You must be signed in to change notification settings - Fork 341
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
ec2_vol: preserve the name tag of the volume #242
ec2_vol: preserve the name tag of the volume #242
Conversation
4b61d98
to
e525866
Compare
@goneri: Greetings! Thanks for taking the time to open this pullrequest. In order for the community to handle your pullrequest effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this pullrequest with this template: |
559c5cd
to
3b7c6e8
Compare
note: Tests need #241 to pass |
3b7c6e8
to
48d8424
Compare
48d8424
to
4e4cba7
Compare
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.
Thanks @goneri!
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.
We specifically want to know that we're not breaking the Name tag or removing tags that we didn't try to set.
I have a preference that we'd expose a "purge_tags" option rather than hard coding either. But I'm good with that being a separate PR (that I'd be willing to raise)
I would prefer to ask the user to use ec2_tag instead. |
https://docs.ansible.com/ansible/latest/dev_guide/platforms/aws_guidelines.html#dealing-with-tags
I think we should chose something and be consistent, updating the doc above to reflect this. The advantage of having the module manage tagging shows up during creation of resources, since it lets you identify them from creation. If we're letting people manage tags on creation it makes sense to have a consistent interface that lets them manage them during the whole lifecycle. |
78d301b
to
98976ab
Compare
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
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.
Apologies if I'm failing to spot it, I don't see an integration test for purge_tags: True
…ons#543) ECS service - add tag+propagate_tags upon creation. SUMMARY this PR is continuation of ansible-collections#242 this PR will enable the use of tags at creation time, in addition to propagate_tags. ISSUE TYPE Feature Pull Request COMPONENT NAME ecs_service ADDITIONAL INFORMATION this PR is continuation of ansible-collections#242 i cant contribute to his repo as i am not a maintainer so i created a new PR, if its not the right git flow please be gentle, its my first time :) Reviewed-by: Mark Chappell <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None>
…ons#543) ECS service - add tag+propagate_tags upon creation. SUMMARY this PR is continuation of ansible-collections#242 this PR will enable the use of tags at creation time, in addition to propagate_tags. ISSUE TYPE Feature Pull Request COMPONENT NAME ecs_service ADDITIONAL INFORMATION this PR is continuation of ansible-collections#242 i cant contribute to his repo as i am not a maintainer so i created a new PR, if its not the right git flow please be gentle, its my first time :) Reviewed-by: Mark Chappell <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None>
…ons#543) ECS service - add tag+propagate_tags upon creation. SUMMARY this PR is continuation of ansible-collections#242 this PR will enable the use of tags at creation time, in addition to propagate_tags. ISSUE TYPE Feature Pull Request COMPONENT NAME ecs_service ADDITIONAL INFORMATION this PR is continuation of ansible-collections#242 i cant contribute to his repo as i am not a maintainer so i created a new PR, if its not the right git flow please be gentle, its my first time :) Reviewed-by: Mark Chappell <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None>
Closes: #229
Closes: #276