Encode name part of resourceId() function to allow name to accept any characters#1188
Merged
SteveL-MSFT merged 7 commits intoPowerShell:mainfrom Oct 21, 2025
Merged
Conversation
1 task
resourceId() function to allow name to accept any characters
tgauth
reviewed
Oct 21, 2025
tgauth
approved these changes
Oct 21, 2025
aab2705 to
8d169db
Compare
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
2 participants
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 Summary
For DSC, the
nameproperty for resources is intended to be a friendly name and not an identity, so we don't have the same restrictions as ARM on what is allowed. Change is to haveresourceId()url encode the name so that arbitrary characters will be encoded and thus allow any character.PR Context
Fix #1186