[New Feature]: Task defintion tags

[yngvark]

Feature Description

It should be possible to tag task definitions.

Problem Statement

When using amazon-ecs-deploy-task-definition, task definitions have no tags.

The AWS API supports setting tags, therefore this action should support it as well. See: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RegisterTaskDefinition.html#API_RegisterTaskDefinition_RequestSyntax

In my case, I register the initial task definition using Terraform, and I put tags on all resources.

When deploying using amazon-ecs-deploy-task-definition, and later running Terraform, it tries to re-apply tags. I don't want this diff.

Alternatives Considered/ Work-arounds

I tried tagging the task definition after it was made by amazon-ecs-deploy-task-definition, but they are immutable, so it is not possible.

Additional Context

I think this comment is the closest I've seen anyone suggest task definition tags in this repository.

Willingness to Contribute

Not sure

[guikcd]

If you use aws-actions/amazon-ecs-render-task-definition version 1.7.0 tags should be get, preserved and passed from the task definition you created.

[rossmotley-genie]

If you use aws-actions/amazon-ecs-render-task-definition version 1.7.0 tags should be get, preserved and passed from the task definition you created.

This worked for me, but I had to use the aws-actions/amazon-ecs-render-task-definition action to download the task definition by setting task-definition-family: name, rather than downloading the JSON myself and passing in a task-definition: task-definition.json.

This is because when downloading a task definition with aws ecs describe-task-definition --task-definition ${{ inputs.service-name }} --query taskDefinition > task-definition.json, even if you include tags with --include TAGS, it puts them outside of the taskDefinition entry in the JSON, so they don't get passed through.