microsoft / microsoft/AzureTRE
Protection of core resources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
We frequently deploy TREs for development alongside our production TRE, which comes with the risk that we may accidentally delete the production TRE if we're in the wrong terminal session when we type the deletion command. It would be great if the management and core resource groups could be locked against accidental deletion once they're deployed, with a flag in the config file to say if you want it locked or not.
I imagine that can be done without impeding the operation of the TRE. Any thoughts?
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
The issue names no files or tests. Start by locating the configuration handling and deployment entry points for the management and core resource groups, then determine how an optional deletion-lock setting can be applied. Done means the setting controls whether those groups are locked while normal TRE operation continues, with coverage for both enabled and disabled configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100