Azure / Azure/azure-rest-api-specs
[BUG] EventHub Geo-DR authorizationRules returns incorrect resource ID without disasterRecoveryConfigs hierarchy
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
Service is returning weird response for disasterRecoveryConfig authorization rule:
url: http://localhost:5000/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/javacsmrg88637/providers/Microsoft.EventHub/namespaces/ns89955b7a/disasterRecoveryConfigs/geodr4035639/authorizationRules?api-version=2024-01-01
response body:
```json
{
"value" : [ {
"id" : "/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/javacsmrg88637/providers/Microsoft.EventHub/namespaces/ns89955b7a/authorizationrules/RootManageSharedAccessKey",
"name" : "RootManageSharedAccessKey",
"type" : "Microsoft.EventHub/Namespaces/AuthorizationRules",
"location" : "southcentralus",
"properties" : {
"rights" : [ "Listen", "Manage", "Send" ]
}
} ]
}
```
the rule id should be something like
`/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/javacsmrg88637/providers/Microsoft.EventHub/namespaces/ns89955b7a/disasterRecoveryConfigs/geodr4035639/authorizationRules/rule1`
(with two ancestors, instead of 1)
Contributor guide
Research direction
Start from the EventHub Geo-DR authorizationRules endpoint shown in the report and inspect its REST API specification. Compare the resource ID hierarchy in the specification with the expected disasterRecoveryConfigs path; done means the returned authorization-rule ID includes both ancestors and validation passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100