fix: fix data race in schema merging logic by creating a copy instead of modifying the original struct instance #397
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Different jobs in terraform-ls use the same
hcl.Block
instance simultaneously and the schema merger modified it in the past.We fixed this by creating a copy first which uncovered another bug: The
buildDynamicBlockSchema
function implicitly read that change from the dependent schema, which we fixed by reading from themergedSchema
instead. This in turn required us to also pass the dependent schema into the function as themergedSchema
also contains the staticlifecycle
block which can't be set via a dynamic block. This means we now iterate over all blocks in the dependent schema but copy their bodies from themergedSchema
.Fixes #395