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
In order to give better feedback to users who have made typos in their variable declarations or definitions, we introduced an error, later demoted to a warning after discussion in #19424, if a .tfvars file includes a definition for a variable that hasn't been declared. We're now recommending the use of environment variables to set "ambient" variable values that made available to all Terraform configurations in a session, since that warning does not apply to those.
However, existing uses with large .tfvars files currently lead to a lot of warnings, because we generate one warning per undeclared variable, and the result is therefore quite overwhelming and redundant. Instead, we should gather all of the undeclared variables into a single list and report a single warning that explains that these should be migrated to use environment variables, using similar text to what we currently have in each individual message.
The text was updated successfully, but these errors were encountered:
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
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to give better feedback to users who have made typos in their variable declarations or definitions, we introduced an error, later demoted to a warning after discussion in #19424, if a
.tfvars
file includes a definition for a variable that hasn't been declared. We're now recommending the use of environment variables to set "ambient" variable values that made available to all Terraform configurations in a session, since that warning does not apply to those.However, existing uses with large
.tfvars
files currently lead to a lot of warnings, because we generate one warning per undeclared variable, and the result is therefore quite overwhelming and redundant. Instead, we should gather all of the undeclared variables into a single list and report a single warning that explains that these should be migrated to use environment variables, using similar text to what we currently have in each individual message.The text was updated successfully, but these errors were encountered: