New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add fixes to keep environments usage within icense limits #1344

Open

4 tasks

nithyatsu opened this issue Jan 7, 2025 · 0 comments

Open

4 tasks

Add fixes to keep environments usage within icense limits #1344

nithyatsu opened this issue Jan 7, 2025 · 0 comments

Labels

on-call

Contributor

nithyatsu commented Jan 7, 2025 •

edited

Loading

Our hosting plan limits to using atmost 10 staging environments.

ref:
https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/db195b18-2f76-4384-a2fe-e4c6b39841b2/resourceGroups/docs/providers/Microsoft.Web/staticSites/radius-docs-edge/environments

https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/db195b18-2f76-4384-a2fe-e4c6b39841b2/resourceGroups/docs/providers/Microsoft.Web/staticSites/radius-docs-edge/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.

nithyatsu added the on-call label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment