microsoft / microsoft/api-guidelines
Add guidelines for RBAC
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
We should provide guidance to Azure service teams on how to design and implement RBAC for their resources.
Some possible sources of material:
- the Azure ARM wiki
- the definition of the ARM RBAC API: https://github.com/Azure/azure-rest-api-specs/tree/master/specification/authorization/resource-manager/Microsoft.Authorization/stable/2015-07-01
- the definition of the KeyVault RBAC API: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.2/rbac.json
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Azure ARM wiki and the linked ARM RBAC and KeyVault RBAC API definitions first. Determine the guidance Azure service teams need for designing and implementing resource RBAC, then publish documentation that clearly covers the agreed recommendations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authorization, documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100