-
Notifications
You must be signed in to change notification settings - Fork 35
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
Migrate all mongodb-awesome-backup
repo code/actions to this repo
#3030
Migrate all mongodb-awesome-backup
repo code/actions to this repo
#3030
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## staging #3030 +/- ##
===========================================
+ Coverage 79.25% 79.34% +0.09%
===========================================
Files 165 165
Lines 13263 13263
Branches 1524 1525 +1
===========================================
+ Hits 10511 10523 +12
+ Misses 2459 2447 -12
Partials 293 293 ☔ View full report in Codecov by Sentry. |
The environment input was added and it's ready for review |
@pdcp1 Please ping me if/when I can retire the old repo. |
4046eb3
into
responsible-ai-collaborative:staging
@smcgregor According to our Slack conversation, @kepae will be in charge of this repo deactivation. |
Part of issue #3023
This PR moves the whole GitHub Actions code from mongodb-awesome-backup to this repo.
It also fixes the broken CSET CSV file export.
The following GitHub Action is added.
.github/workflows/db-backup.yml
This action is responsible for generating the DB backup and DB snapshots.
New GitHub Actions environment secrets needed
These Cloudflare credentials must have write permissions
secrets.CLOUDFLARE_R2_WRITE_ACCESS_KEY_ID
secrets.CLOUDFLARE_R2_WRITE_SECRET_ACCESS_KEY
Testing
This code can be tested on Pablo's environment https://github.com/pdcp1/aiid/actions/workflows/db-backup.yml
Release considerations
Both GitHub Actions (
Public backup to the cloud
andPrivate backup to the cloud
) on the original repo should be disabled as soon as we release this PR into Production.