You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case: It becomes tedious keeping multiple environment variables in sync when working with terraform + another tool (or set of tools) that use environment variables for configuration. Today, I need to make sure ENDPOINT=abc is set for tool x, and TF_VAR_endpoint=abc is set for terraform. Allowing this override would remove this (albeit small) pain point.
I'd be happy to tackle this feature - but first wanted to get input from some of the core members in case this has deeper implications I'm not seeing.
The text was updated successfully, but these errors were encountered:
Duplicate of #62, closing for now. I believe @mitchellh may have more to add, but it's definitely a topic that's talked about internally quite often. There are still a few core issues with adding environment variable interpolation at this stage. It's definitely something we wish to target in the future, as it's a heavily requested feature. Thanks!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 17, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to allow an optional override of the default
TF_VAR_
environment variable mapping inside thevariable
block:My use case: It becomes tedious keeping multiple environment variables in sync when working with terraform + another tool (or set of tools) that use environment variables for configuration. Today, I need to make sure
ENDPOINT=abc
is set for tool x, andTF_VAR_endpoint=abc
is set for terraform. Allowing this override would remove this (albeit small) pain point.I'd be happy to tackle this feature - but first wanted to get input from some of the core members in case this has deeper implications I'm not seeing.
The text was updated successfully, but these errors were encountered: