Feature Request: Global environment variables

[bverkron]

Is your feature request related to a problem? Please describe.
When I need to use the same environment variable in several stacks it's annoying to have to re-define and populate that variable in each stack individually. It's additionally frustrating when that variable needs to be changed and I have to go into each separate stack to change it. I'm human and I can miss some or make mistakes. :)

Describe the solution you'd like
It would be helpful to have a global area to define / load environment variables into and then maybe a toggle or other mechanism to specify whether a stack should load those global environment variables.

Describe alternatives you've considered
Not sure :/

Additional context
One example of common variables I need in several stacks is credentials for a remote mail server for sending notifications. Another is backup configuration values for a docker-volume-backup sidecar container I have in almost all my stacks (10+). Much of that configuration is the same across all instances of that sidecar container and I have to go into each of the 10+ stacks and configure the same thing and then do it all again if I have to add a new env value or modify one. Quite painstaking.

[bverkron]

#7474 might be related development wise. Global variables, if implemented, should work in conjunction with "local" variables at the stack level and one should not override the other.

[github-actions[bot]]

This issue has been marked as stale as it has not had recent activity, it will be closed if no further activity occurs in the next 7 days. If you believe that it has been incorrectly labelled as stale, leave a comment and the label will be removed.

[bverkron]

Would still like this feature.

[ehosch]

I would like this feature as well.

[ThaDaVos]

Any up date on this?

This feature request can help in so many scenario's to ease configuration of multiple stacks etc

[jruiz94]

I'd like this feature also

[cloudmaker97]

This feature would be so awesome, so all my nodes containing (mostly) backup nodes like the thread owner also do. If i need to rollout a new key it would be faster and efficient to just manage them in one single place and keep the good stack-management.

[gcstr]

It makes no sense that this isn't a feature after so many years.