tarantool / tarantool/migrations
API to get migration status of a cluster.
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 20
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
People sometimes forget to do migrations.up() after cluster upgrades.
It would be nice to get a flag that all migrations are up to date and possibly display it as an issue in Cartridge UI ifl not all migrations are applied or MD5 of file differs from original.
This will also require to compute hash (for example MD5) of each migration and store it when migration is applied successfully.
See for example https://docs.liquibase.com/commands/community/status-verbose.html
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
Start by reviewing the migration application and persistence paths, then compare the requested status API with Liquibase's status-verbose behavior. Define how applied migration hashes are stored, how changed files are reported, and how Cartridge UI would consume the result; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100