feat: Allow experiments from override files to be used
#38011
Closed
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.
PR illustrating an approach to fixing #38012, but what the solution is is still up for debate.
Terraform allows the use of override files to change configuration while leaving the original configuration unedited. Overrides are compatible with the
terraformblock, but each setting inside that block has slightly different behaviour. For examplerequired_providersis merged between the original config and the override config, whereas abackendorcloudblock in the override config completely replaces the original config'sbackendorcloudblock.This PR allows the
experimentsfield from theterraformblock to be used from override files. The merging behaviour is additive, so experiments present in both the original config and the override config will be active in the final parsed configuration.Currently any
experimentsconfiguration in the override file is silently ignored.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