mayadata-io / mayadata-io/oep-e2e
(feat): Pipeline to test compatibility of dop releases with version changes.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
It was observed that there can be two types of changes in database schema which are responsible for DB migration and data migration in MySQL.
If in the releases there were subsequent such migration it can cause issues so the user cannot directly upgrade to the latest image. User needs to do a sequential upgrade in such cases.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or entry points are named. Start by locating the existing release-testing pipeline and the MySQL migration scenarios, then define coverage for sequential upgrades when releases contain schema or data migrations; done means the pipeline detects incompatible direct upgrades and verifies the required upgrade sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, python
- Domain
- ci-cd, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100