Fix for incorrect error diagnostic on policyDefinitions existing resource usage#18169
Merged
Conversation
Contributor
|
Test this change out locally with the following install scripts (Action run 18227599251) VSCode
Azure CLI
|
anthony-c-martin
approved these changes
Oct 3, 2025
Contributor
Dotnet Test Results 96 files - 48 96 suites - 48 41m 40s ⏱️ - 28m 51s Results for commit 9aa2b60. ± Comparison against base commit 066c054. This pull request removes 1920 and adds 654 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
anthony-c-martin
approved these changes
Oct 3, 2025
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.
Quick fixes for issues: 18163 & 18163
ValidParentScopes must contain scopes that can be written to and read from. The broken implementation only passed in scopes that could be written to, hence breaking customers who tried to use the
existingkeyword with a scope that could be written to and read from.Root cause of the issue is that ResourceTypeComponents has a property named "ValidParentScopes", which is intended to capture both writable and readable scopes, but the type loading code was updated to be more precise about differentiating readable + writable scopes, and misinterpreted this field to just mean "writable scopes" (see here)
Microsoft Reviewers: Open in CodeFlow