microsoft / microsoft/AzureTRE
Shared services should live in their own resource groups
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
To enable clear separation between deployed artefacts the shared services should be deployed into their own resource groups. When deleting shared services, it is therefore clear to see if the shared service has been successfully removed.
This also means shared services can receive delegated rights to the resource group if required to enable them to create new resources.
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
No files, tests, or entry points are named in the issue. Start by locating how AzureTRE deploys shared services and assigns resource groups, then verify that each shared service is isolated in its own group, can be clearly removed, and supports delegated rights where required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100