What would you like to be added:
The ability to pass tags []types.Tag to the RegisterTaskDefinition function inside the ECS platform provider (pkg/app/piped/platformprovider/ecs/client.go), and propagate them to the AWS ECS SDK ecs.RegisterTaskDefinitionInput.
Currently, there is an explicit // TODO: Support tags for registering task definition. left in the codebase at line 202.
Why is this needed:
AWS relies heavily on tags for cost allocation, organization, and IAM resource-level permissions. Discarding tags at the task definition registration phase breaks parity with AWS best practices, preventing teams from effectively tracking costs and managing their deployed resources directly via PipeCD metadata. I've noted this gap while working with the generic provider schemas.
What would you like to be added:
The ability to pass
tags []types.Tagto theRegisterTaskDefinitionfunction inside the ECS platform provider (pkg/app/piped/platformprovider/ecs/client.go), and propagate them to the AWS ECS SDKecs.RegisterTaskDefinitionInput.Currently, there is an explicit
// TODO: Support tags for registering task definition.left in the codebase at line 202.Why is this needed:
AWS relies heavily on tags for cost allocation, organization, and IAM resource-level permissions. Discarding tags at the task definition registration phase breaks parity with AWS best practices, preventing teams from effectively tracking costs and managing their deployed resources directly via PipeCD metadata. I've noted this gap while working with the generic provider schemas.