SSWConsulting / SSWConsulting/SSW.Website
💸 Tech Debt - Lock Azure resources for any accidental deletion
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Description
As we constantly create and delete slots for PR through our pipeline and sometimes we do manually from the Azure Portal for rg - ssw.com.au. Therefore, we should place a lock constraint on App Service's main slot to avoid any accidental delete.
Figure: Lock option for App Service
Proposed solution
We can simply add the constraint on the main slot but that will be inherited by the prospective slots that could cause an error while deleting the slots after being merged with the main branch.
We need to find a way to avoid that lock's inheritance while running our bicep for the PR deployment which could solve the issue.
### Tasks
- [ ] Investigate the solution
- [ ] Avoid any lock's inheritance being passed from the main slotContributor 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
Start with the Bicep used for PR deployment and the Azure App Service main slot resource, then review how resource locks are inherited by prospective slots. Test the deployment and slot-cleanup flow; done means the main slot is protected while merged PR slots can still be deleted without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100