Create pipeline action to test migrations against prod backup in secure environment
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue names no files, tests, or existing pipeline entry point. First map how migrations and deployment automation currently run, then identify how a production backup can be accessed and tested in a secure environment. Done means a pipeline action reliably tests migrations against a production backup before deployment without exposing the backup.
Written by the indexing model from the issue text.
Description
We test migrations against many copies of the db during development and usually catch any gotchas, but to be extra safe one should always be tested against a prod backup prior to deploying. This solution would do just that.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bcgov/range-api
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
Renew MyRange SSL certificate (expires Apr 14, 2027)Possibly taken @brijesh-amin claimed this 7 days ago. Open
-
#523 - Reduce any usage in db2 model/query layerMay be free again @brijesh-amin claimed this 80 days ago, and no pull request is open. Open
-
#523 - TypeScript hardening for runtime-critical pathMay be free again @brijesh-amin claimed this 80 days ago, and no pull request is open. Open
-
#523 - Centralize and type environment configurationMay be free again @brijesh-amin claimed this 80 days ago, and no pull request is open. Open
Similar issues
-
area:docs bug triage:confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#2875 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#8862 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated oneOpendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
konflux-ci/konflux-ui#1596 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day