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

Propagate tags to ECS tasks #732

Open
rocketnova opened this issue Aug 14, 2024 · 0 comments
Open

Propagate tags to ECS tasks #732

rocketnova opened this issue Aug 14, 2024 · 0 comments
Labels
scope: service Service layer / component type: feature New feature or new functionality to existing feature workflow: good first issue Good for newcomers workflow: self-contained Doesn't require a lot of context to pick up

Comments

@rocketnova
Copy link
Contributor

The terraform resource aws_ecs_service has an optional propagate_tags argument. If we set this to TASK_DEFINITION or SERVICE, the tags of the task definition or service will get attached at creation to the task. I think it doesn't matter whether we choose SERVICE or TASK_DEFINITION since we use the same tags on both, but here's a stack overflow explaining the difference.

The implementation should verify that setting this argument works as expected.

References

Here's the AWS documentation.

Currently, tags on the task definition look something like this:

Currently, tasks have no tags:

Here's what the AWS Console interface looks like for this setting:

@rocketnova rocketnova added type: feature New feature or new functionality to existing feature workflow: good first issue Good for newcomers scope: service Service layer / component workflow: self-contained Doesn't require a lot of context to pick up labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: service Service layer / component type: feature New feature or new functionality to existing feature workflow: good first issue Good for newcomers workflow: self-contained Doesn't require a lot of context to pick up
Projects
None yet
Development

No branches or pull requests

1 participant