PSS: Ensure experimental backend codepath is isolated + gated correctly #37868
+228
−132
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.
This just moves the code that was added to
init.gosince 7f29df9https://github.com/hashicorp/terraform/commits/main/internal/command/init.go
The goal is to better isolate the experimental codepath and reduce the risk of breaking things in the non-experimental ones.
Additionally, the PR also updates the condition and diagnostic wording to ensure it is gated not just behind experimental build but also behind the feature CLI flag.
I ran into a somewhat confusing/misleading diagnostic myself on
initwhich motivated this PR: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