You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a Microsoft.Bing resource fails for existing resource groups with special characters in the name, such as Japanese 西日本, due to pattern validation on the resource group name.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Pattern","message":"String does not match pattern ^[-\\w\\._\\(\\)]+$: 西日本. Paths in payload: '.path.resourceGroupName'"}]}
It is using the common ResourceGroupNameParameter which has that pattern:
arwong
changed the title
Resource group name fails pattern when creating resources
Resource group name fails common-types pattern when creating resources
Apr 30, 2021
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.
Issue Details
Creating a Microsoft.Bing resource fails for existing resource groups with special characters in the name, such as Japanese 西日本, due to pattern validation on the resource group name.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Pattern","message":"String does not match pattern ^[-\\w\\._\\(\\)]+$: 西日本. Paths in payload: '.path.resourceGroupName'"}]}
It is using the common ResourceGroupNameParameter which has that pattern:
Creating a Microsoft.Bing resource fails for existing resource groups with special characters in the name, such as Japanese 西日本, due to pattern validation on the resource group name.
It is using the common ResourceGroupNameParameter which has that pattern:
azure-rest-api-specs/specification/common-types/resource-management/v1/types.json
Line 553 in c2ea3a3
Note that this is the same problematic regex as in #13136 but in a different file.
The text was updated successfully, but these errors were encountered: