radius-project / radius-project/docs
Add fixes to keep environments usage within icense limits
Open
Nobody has claimed this yet.
on-call
triaged
- Dominant language
- Bicep
- Stars
- 26
- Forks
- 52
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
Our hosting plan limits to using atmost 10 staging environments.
In order to not run into issues,
- We should add nightly job (or another frequency to be decided) which should delete old/unused environments.
- We should create issues when clean up / setup fails, so that the orphaned environments could be manually cleaned up
- We should provide on-call with the permissions to delete orphaned environments.
- Add a step in the beginning of the workflow to check for orphan resources and delete them as needed.
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 workflow entry points are named in the issue. Start by locating the environment setup workflow and its Azure Static Web Apps integration, then determine how cleanup, failure reporting, permissions, and orphan-resource checks should fit together. Done means the listed safeguards keep staging environments within the 10-environment limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100