Fix Azure Resource ID sanitization documentation inconsistencies #477
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.
Documentation and test comments incorrectly stated that Azure Resource IDs use '-' (hyphen) for sanitization, when the actual implementation uses '_' (underscore). This created confusion about the dual ID architecture where
clusterIdmust never contain '/' characters.Changes:
BaseClusterModel.tsandcopilot-instructions.mdto correctly document that '/' is replaced with '_' in sanitized IDsBaseClusterModel.test.tsandAzureClusterModel.test.tsto explicitly show bothclusterIdandtreeIdare sanitized for Azure/Discovery ViewsoutputChannelWarnMockvariable and fixed lint error inDiscoveryBranchDataProvider.test.tsExample:
All documentation now consistently reflects that the original unsanitized Azure Resource ID is preserved in
AzureClusterModel.idfor Azure API calls, whileclusterIdandtreeIduse the sanitized version with underscores.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.