registry/.github/workflows
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Radoslav Dimitrov 8de5283995
Introduce a cron job that syncs the prod base into staging (#633)
<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR adds a workflow that should:
* Runs daily but also can be manually triggered
* Drops the staging database and copies the prod database into it

This should improve our release confidence by reducing the likelihood of
regressions or unexpected breakages.
 
Copy from Claude:
```bash
What This Does:

1. Connects to prod → Extracts backup credentials
2. Switches to staging → Configures backup access
3. Creates restore PVC → 50GB temporary storage
4. Triggers k8up restore → Downloads latest prod backup
5. Waits for restore → With proper job discovery
6. Finds PostgreSQL PVC → Dynamically
7. Scales down DB → Safely
8. Copies data → With validation and backup
9. Scales up DB → With pod creation waiting
10. Verifies DB → Tests tables and queries
11. Cleans up → Removes temporary resources
```

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->
No

## Breaking Changes
<!-- Will users need to update their code or configurations? -->
No (I assume no one relies on staging keeping its state)

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

---------

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Co-authored-by: Adam Jones <adamj@anthropic.com>
2025-10-09 12:01:39 +01:00
..
cancel-pulumi-lock.yml build(deps): bump pulumi/actions from 6.5.0 to 6.6.0 in the actions group (#593) 2025-10-01 10:43:27 +01:00
ci.yml build(deps): bump actions/cache from 4.2.4 to 4.3.0 in the actions group (#545) 2025-09-25 12:40:28 +00:00
claude.yml chore: remove outdated version tags from GitHub Actions (#457) 2025-09-12 13:51:46 -07:00
deploy.yml build(deps): bump pulumi/actions from 6.5.0 to 6.6.0 in the actions group (#593) 2025-10-01 10:43:27 +01:00
release.yml build(deps): bump docker/login-action from 3.5.0 to 3.6.0 in the actions group (#577) 2025-09-30 09:32:16 +03:00
sync-db.yml Introduce a cron job that syncs the prod base into staging (#633) 2025-10-09 12:01:39 +01:00