Azure / Azure/azure-rest-api-specs
KeyVault RBAC RoleDefinitionProperties `assignableScopes` not working as expected
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
when i create a RoleDefinition for a ManagedHSM for assignableScopes field as described here:
https://github.com/Azure/azure-rest-api-specs/blob/9e17eb2d475e8908277d929b0e4a4c582e2ba752/specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.4/rbac.json#L624-L629
if i pass a `/keys` to Create Method, the response of this field changed to `/`. Is this a by-design or this property does not support the vaule of `/keys`?
Request:
Response:
**Enum** defined the `/keys` value:
https://github.com/Azure/azure-rest-api-specs/blob/9e17eb2d475e8908277d929b0e4a4c582e2ba752/specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.4/rbac.json#L682-L689
Contributor guide
Research direction
Start by reading specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.4/rbac.json, especially the assignableScopes definition at lines 624-629 and its enum at lines 682-689. Compare the documented /keys value with the reported request and response, then determine whether the behavior is expected or whether the specification needs correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, json
- Domain
- api, authorization, cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100