Closed b-per closed 4 months ago
I was actually able to close #99 without this, so this becomes a lower priority
This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Is your feature request related to a problem? Please describe.
Related to #221
Today, the
environment_variable
resource contains the value for all the scopes (in this issue, scope will represent the "project" scope or any named environment, e.g. "Dev", "CI", "Prod" etc...)This means that we can't set a single env var from different Terraform projects, using different states.
Describe the solution you'd like
It might be beneficial to create a new resource
environment_variable_scope
where the "grain" of the resource would be the value of the env var for a given scopes rather than for all scopes.In that case, we could set the values of a single environment variable from different Terraform project.
Describe alternatives you've considered
I am not sure if this would be required by many people, and/or if we could just keep only the existing
environment_variable
resource.I am also not clear yet whether this would help with #99
Additional context
This idea/requirement came from a discussion with a customer wanting to create different environments for different feature branches, each environment being in its own Terraform project/state.