migratus
migratus copied to clipboard
yogthos
Allow for future migrations that are not run until the timestamp on the migration has passed
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.
That sounds like it would be a reasonable idea. Should be easy enough to pass an additional flag for this and then filter against it when selecting the migrations to run.
I can take care of it. Do you want two flags? 1 for migratus/create to generate the future timestamp, and 1 for migratus/migrate to skip future migrations?
Sounds great, and that would make sense, maybe create could take an additional argument to specify the start time explicitly then and if it's provided use that instead of generating the timestamp.
Sounds great, and that would make sense, maybe create could take an additional argument to specify the start time explicitly then and if it's provided use that instead of generating the timestamp.
For which of the functions?
(mig/create {:future-days 30} title :edn)
(mig/migrate {:to :now})
(mig/migrate {:to "20230526202953"})
??
This could be added later, but I wouldn't do it in this pr.
(mig/rollback {:to "20230526202953"})
Yeah, I think human readable format would be ideal here for create. :) And migrate to :now or explicit timestamp sounds good.
Default to :now or not? Its bordering on breaking, but I would also guess that with mig/create, no one is making future dates manually.
I think defaulting to :now would be reasonable, that's basically the implicit behavior right now.
I think defaulting to
:nowwould be reasonable, that's basically the implicit behavior right now.
Perfect. That is what I was thinking too.