Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Waarp Manager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 165
    • Issues 165
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Applications
  • Waarp Manager
  • Waarp Manager
  • Issues
  • #333
Closed
Open
Created May 06, 2022 by Bruno Carlin@bruno.carlinOwner

Enhance migration rollbacks

To Rollback the database to a previous version, a user must know its internal identifier. There is however no way to discover these ids.

This can be solved by adding:

  1. aliasing the latest migration of a version to the name of that version to ease migrations and rollbacks:

    # Instead of 
    waarp-manager db migrate down 20220228
    # do
    waarp-manager db migrate down 0.15.0
    
    # Instead of 
    waarp-manager db migrate up 20220423
    # do
    waarp-manager db migrate up 0.16.0
  2. a list subcommand to migrate to list all known migrations. For example:

    $ waarp-manager db migrate list
    0.16.0   20220423   Does foo
             20220301   Does bar
    0.15.0   20220228   Does baz
    [...]
Assignee
Assign to
Time tracking