Skip to main content

Worker pool controller exposes more environment variables

Feature RequestsWorkersKubernetes

Would be great if worker pool controller could expose more contextual SPACELIFT_ environment variables such as stack slug, space ID/name, etc. It could be helpful for various use-cases, but a particular one we have in mind is breaking down the private workers consumption for analytics purposes, so we would know how many private minutes were spent by which stacks and spaces.

Workaround
No
Status: 🗑️ Archived7 comments

Log in to comment and vote

Comments7

  • Black Breeze

    •

    Sep 29, 2025

    Hey Dmytro! Thanks for taking the time to fill out the feature request.

    Can you please clarify a few things:

    • where would you want these variables available - in the worker pool controller process, or in the run container itself?

    • if the latter, is there a reason why TF_VAR_ variables would not work? They have a special meaning to OpenTofu/Terraform, but they’re regular environment variables, too, and can be reused for any purpose, like analytics you’re mentioning.

    Thank you in advance!