-
Notifications
You must be signed in to change notification settings - Fork 10.2k
stacks: Add local values walk to walk_dynamic #37980
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This helps us catch diagnostics in locals that only happen during evaluation Co-authored-by: Mutahhir Hayat <[email protected]> Co-authored-by: Matej Risek <[email protected]>
nfagerlund
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Omg awesome, I was hoping you'd be able to track down a way to interrupt this.
I went ahead and re-ran my reproduction case, and sure enough, the plan errored and spewed the same list of errors I saw from the modules runtime into the diagnostics. I was unable to proceed to an apply and corrupt the state.
The empty state thing still definitely deserves love, but this definitely fixes the one cause of it that we've been able to observe.
|
@nfagerlund I'll also look into the state issue and in inputs being unknown to make sure no other way can lead to a similar issue |
|
@nfagerlund This PR should fix the state issues: #37981 |
e02f8b4
This helps us surface issues where we can only notice problems with local values in the stacks component language during the evaluation of the value.
Co-authored-by: Mutahhir Hayat [email protected]
Co-authored-by: Matej Risek [email protected]
Fixes #
Target Release
1.15.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry