-
Notifications
You must be signed in to change notification settings - Fork 127
chore(ci): add cleanup script on CI for atlas envs #608
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds automated cleanup functionality for stale Atlas test environments by introducing a nightly CI job that removes old test projects and their associated clusters.
- Implements a cleanup script that identifies and removes test projects older than 24 hours
- Adds a GitHub Actions workflow that runs the cleanup script nightly via cron schedule
- Provides manual trigger capability through workflow_dispatch for on-demand cleanup
Reviewed Changes
Copilot reviewed 2 out of 8 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
scripts/cleanupAtlasTestLeftovers.test.ts | Implements the cleanup logic to find and delete stale Atlas test projects and clusters |
.github/workflows/cleanup-atlas-env.yml | Defines the CI workflow that runs the cleanup script on a nightly schedule |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Pull Request Test Coverage Report for Build 18194665523Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Proposed changes
Runs a nightly script that cleans up stale test environments. This is necessary because in cloud-env there might be hiccups and tell a cluster was going to be deleted but then it's not.
Checklist