Question: cost attribution per team/repository recommendation

[kgoralski]

Hey,

I wonder if you got some recommendation on dynamic EC2 tagging of self-hosted runners for cost exploring. Like per team/repository.

With multiple teams and repositories setup It would be great to for example on Job got started it got tagged additionally with tags like team, repository etc. Ideally it could be some extra tags on GH workflows side that could be picked up by scale-up lambda that could update the tags dynamically?

Maybe it could be extended with usage of these variables?

https://github.com/philips-labs/terraform-aws-github-runner/blob/main/modules/multi-runner/variables.tf#L64

terraform-aws-github-runner/modules/multi-runner/variables.tf

Line 80 in e269d0f

runner_ec2_tags = optional(map(string), {})

Thanks in advance for the answer

[npalm]

With ec2 tags (and multi-runners) you can tag per runner type. Tagging per job is not supported. I think this can be done by using a pre job script that is using the job event to add a tag to the instance.

For repo level runners tagging could also be done via the lambda, but not sure if this is supported by the module. For org level runners this won't work since creating a runner based on an event does not match which job got assigned by GitHub.

[kgoralski]

Tagging per job is not supported

Do you think that it could be nice feature or it's something out of the scope?

I guess the code below is the right place to look for to extend that?

https://github.com/philips-labs/terraform-aws-github-runner/blob/main/modules/multi-runner/variables.tf#L64

terraform-aws-github-runner/modules/multi-runner/variables.tf

Line 80 in e269d0f

runner_ec2_tags = optional(map(string), {})

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs. Thank you for your contributions.