Akhilailla/fix false alarm for resource name restriction. #645
Conversation
This file contains 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
added 2 commits
January 12, 2024 13:40
… into akhilailla/fix_false-alarm_for_ResourceNameRestriction
bdefoy
reviewed
Jan 13, 2024
...idator-rulesets/akhilailla-fix_false-alarm_for_ResourceNameRestriction_2024-01-12-19-39.json
Show resolved
Hide resolved
AkhilaIlla
deleted the
akhilailla/fix_false-alarm_for_ResourceNameRestriction
branch
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.
The ResourceNameRestriction linter rule flags an error for system defined types such as privateEndpointConnections, which is a false-alarm.
This PR excludes system-defined parameters from being considered in the validation