Open
Description
API Version: 2022-08-29
Some resource IDs are being treated as case sensitive in requests, I believe this to be an error as my understanding is that the ARM spec expects ID's in requests to be case-insensitive on request, but case sensitive in response?
For example, in this LRO polling response
{"id":"/providers/PaloAltoNetworks.CloudNGFW/locations/WESTEUROPE/operationStatuses/d465ddf7-1ccb-4475-9b8d-8b093528faa8*4CAB51C5DA54805C08A62167BB8AB0905594C452830FD2502B164239A40719E8","name":"d465ddf7-1ccb-4475-9b8d-8b093528faa8*4CAB51C5DA54805C08A62167BB8AB0905594C452830FD2502B164239A40719E8","resourceId":"/subscriptions/[REDACTED]/resourceGroups/acctestRG-CAE-230711165837794803/providers/PaloAltoNetworks.CloudNGFW/localRulestacks/testAcc-palrs-230711165837794803","status":"Failed","startTime":"2023-07-11T15:00:37.3304758Z","endTime":"2023-07-11T15:02:05.7671482Z","error":{"message":"Invalid parameter: Rulestack arm id format is incorrect. Expected format: /subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/PaloAltoNetworks.Cloudngfw/localRulestacks/RS_NAME with status code BadRequest"}}
Request has: PaloAltoNetworks.CloudNGFW
API requires: PaloAltoNetworks.Cloudngfw
In this case, this was an update payload to the RuleStacks CreateOrUpdate method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Workflow: This issue is responsible by Azure service team.Issues that are reported by GitHub users external to the Azure organization.Workflow: This issue needs attention from Azure service team or SDK teamThe issue doesn't require a change to the product in order to be resolved. Most issues start as that