migrator

Documentation

Index

• func DestructiveMigrateForTests(pgURL, migrationsPath string, l logger.Logger, verbose bool) error
• func Drop(pgURL, migrationsPath string, l logger.Logger, verbose bool) error
• func Migrate(pgURL, migrationsPath string, l logger.Logger, verbose bool) error
• func MigrateWithMigrationsTable(pgURL, migrationsPath, migrationsTable string, l logger.Logger, verbose bool) error

Functions

func DestructiveMigrateForTests

func DestructiveMigrateForTests(pgURL, migrationsPath string, l logger.Logger, verbose bool) error

DestructiveMigrateForTests will: * Drop the database to give you a clean slate * Run all your migrations * Forcibly run all the migrations again to verify that they are idempotent.

Obviously you don't want this for production, but you should use it instead of the plain Migrate function in your tests if you can.

func Drop

func Drop(pgURL, migrationsPath string, l logger.Logger, verbose bool) error

func Migrate

func Migrate(pgURL, migrationsPath string, l logger.Logger, verbose bool) error

Migrate executes all migrations we have Addind the filePath check in the below code to avoid the execution for the Migation code on the other than First Frontend node. Migration code will execute on the First node (Bootstrap_automate node) On the remaining node migration code execution is not required

func MigrateWithMigrationsTable

func MigrateWithMigrationsTable(pgURL, migrationsPath, migrationsTable string, l logger.Logger, verbose bool) error

MigrateWithMigrationsTable executes all migrations we have, using the specified migrations table.