feat(ecs): add AWS task tag support#107
Merged
Merged
Conversation
Adds a `tags` field to the ECS cluster, command, and job contexts so operators can attach arbitrary AWS resource tags to ECS tasks at launch. Tags are merged in precedence order (cluster < command < job), and `job_id` is always injected automatically so every task is traceable back to its Heimdall job. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sanketjadhavSF
approved these changes
Jun 4, 2026
prasadlohakpure
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tagsfield to the ECS cluster context, command context, and job context so operators can attach arbitrary AWS resource tags to tasks at launchjob_idis always injected automatically so every ECS task is traceable back to its Heimdall jobHow it works
Tags from all three levels are resolved once in
buildExecutionContextbefore any tasks are launched:json.Unmarshalmerges map fields, so command and job tags are already merged by the time they reach the execution context)job_idis set last and cannot be overriddenExample config
Resulting ECS task tags:
env=prod,cluster=ecs-fargate,team=data-platform,pipeline=my-pipeline,job_id=<heimdall-job-id>Test plan
job_idtag is always present