microsoft / microsoft/sre-agent
Managed resources chicken & egg problem (RBAC)
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 160
- Forks
- 97
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 12
Description
We use IaC for everything which also means the SRE agent. With multiple teams managing their own resources, onboarding SRE agent creates a chicken and egg or ownership issue.
Either we need to structure this so SRE's role to the managed resources are defined in the SRE repo. However, teams managing their own code often wants their RBAC to be defined within their definition.
Granting SRE permissions to resources does not automatically add them as a managed resource. So changes might need to happen in multiple places for onboarding. How do other solve this?
Im leaning towards everything defined in the SRE configuration for simplicity..
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or implementation entry points are identified. Clarify whether RBAC ownership should live in the SRE configuration or each team's resource definition, then document the chosen onboarding and managed-resource behavior as the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- authorization, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100