yogthos/migratus

Allow for future migrations that are not run until the timestamp on the migration has passed

Open

#243 opened on Jun 20, 2023

View on GitHub
 (10 comments) (1 reaction) (0 assignees)Clojure (99 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (686 stars)
PR merge metrics
 (PR metrics pending)

Description

Add an optional input to migratus/create that sets the date X days in the future, and then update migratus/migrate to skip those.

The use case is for when the table structure changes so that there is an old table or column that needs to be cleaned up. This would let me create that clean up for 30 days when I know all the other code changes have taken place.

Contributor guide

Research direction
Understand the current migratus migration mechanism, focusing on how migration timestamps are used. Then implement an optional :future days parameter in the create function that records a future timestamp. Modify the migrate function to skip migrations whose scheduled time is in the future.
Tech stack
None
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ClojureGitDatabase migration concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75