Fully parse input variables from TF_VAR_ when validating during apply
#36121
Conversation
jbardin
added
the
1.10-backport
Input variables taken from the environment have no type information, so are initially stored as strings. When we compare those for validation during apply, we have to make sure to use the same parsing logic used in the plan in order to compare them with the stored variables.
Non-string input variables taken from the environment initially need to be parsed and stored as string, since there is no type associated type information. Make sure these are correctly handled when validated during apply.
jbardin
force-pushed
the
jbardin/apply-env-vars
branch
from
5997797 to
4883499
Compare
|
Hey @jbardin thank you for the work! Is there anything blocking from merging? Thanks :) |
|
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
|
has this been merged into the release v1.10? We're still seeing the error but want to make sure its because it simply hasn't been released into the wild yet |
|
@jonathandbyrd, no there has not yet been a v1.10.1 release yet, but that should be scheduled soon. |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Input variables taken from the environment have no type information, so are initially stored as strings. When we compare those for validation during apply, we have to make sure to use the same parsing logic used in the plan in order to compare them with the stored variables.
Fixes #36106