Repository navigation
fix: restrict property validation to reachable regional scenarios - #4756
Open
proton0210 wants to merge 2 commits into
Open
proton0210 wants to merge 2 commits into
proton0210 wants to merge 2 commits into
Conversation
proton0210
marked this pull request as draft
October 21, 2026 06:07
proton0210
marked this pull request as ready for review
October 21, 2026 06:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #4746.
Region-specific conditions previously allowed property validation to inspect branches and resources that cannot exist in the selected region. Constrain condition scenarios per region, including when provider schemas are shared, and carry those constraints through property and gathered-resource checks. Validate primary identifiers separately for each region and correct the legacy region-scenario Cartesian product.
Preserve condition metadata across evolution and keep intentional regional branches from producing universal unreachable-branch warnings. Regression coverage includes all five reported templates, mixed-region runs in both orders, nested conditions, and contradictory regional combinations. Update existing expectations only for findings on branches or resources excluded in the linted region.
Validation: the full unit suite and focused integration checks passed. Three audit passes covered upstream reproduction, non-regression/edge-case checks, and final combined source review (3,027 unit/integration tests passed plus the separate schema-updater test; four data tests retain the default exclusion).