Migrating to Goose - How to "skip" migrations?

[cjtheham]

I'm migrating to Goose from a separate migrations setup and plan to import all the previous migrations - is there a way I can get Goose to "know" that the database is on one migration without it running goose up?

[TArch64]

Have the same issue. It would be nice to have a command to mark migrations as completed. Ideally it can be a command to pull state from a database and save to migration file

[cjtheham]

@TArch64 The solution I came up with, since what I need to skip is a prod deployment, is running all migrations locally and saving the data in the table Goose creates to copy it to prod. Maybe that'll help you, but I'd still like an easier way to do it personally...

[TArch64]

Thank you. I was thinking about the same solution

[TArch64]

I see there is pull request that may be helpful #954

[mfridman]

Yeah, I want to add this feature. So it's definitely in the "up next" pile.