Tags not being passed to fargate tasks/containers #2698
MIJOTHY-V2
started this conversation in
Artillery
Replies: 1 comment
-
The Converting to discussion. Tagging AWS resources is a valid use-case but the flag is working as intended right now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version info:
Running this command:
I expected to see this happen:
run-fargate
job logs output the tagsInstead, this happened:
Additional Context
These tasks are running on a pre-existing untagged cluster, but the lack of tags there is fine for us, as we mainly want to distinguish between different artillery test runs on the same cluster using tags.
Thoughts
A very brief look at some of the source seems to point to
context.tags
being correctly picked up by artillery, hence the job logs emitting the relevant tagsartillery/packages/artillery/lib/platform/aws-ecs/legacy/run-cluster.js
Lines 636 to 639 in af8834b
but not being passed to the created AWS resources here
artillery/packages/artillery/lib/platform/aws-ecs/legacy/run-cluster.js
Lines 1590 to 1602 in af8834b
or here
artillery/packages/artillery/lib/platform/aws-ecs/legacy/run-cluster.js
Lines 1634 to 1660 in af8834b
Beta Was this translation helpful? Give feedback.
All reactions