Add MongoDB production data sync CronJob for non-production environments #2965
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds a Kubernetes CronJob that syncs MongoDB production data to non-production environments by downloading the latest private dump from GCS and restoring it to the target database.
Code Changes
helm-chart/sefaria/templates/cronjob/sync-mongo-production-data.yaml: New CronJob templateprivate_dump_*.tar.gzfromgs://sefaria-mongo-backup/(excludesprivate_dump_small_*)mongorestore --drop30 12 * * *(daily at 12:30 PM)restore.enabled && cronJobs.syncMongoProductionData.enabledhelm-chart/sefaria/values.yaml: AddedcronJobs.syncMongoProductionData.enabled: falseNotes
Disabled by default. Requires service account with GCS bucket read access (
restore.serviceAccount). Uses GCS timestamps for reliable latest-backup detection.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.