It might be nice to optionally have some sort of guard rail or required confirmation step for production migrations. I typically use ctrl+r to get my migrate command from my shell history. It is too easy to accidentally get and run the production migrate command when wanting to migrate development.
It would be nice to have a confirmation step that required typing the name of the environment.
This could be toggled in the config files locally or with a special table remotely. Local config might be simpler, but it could be more difficult when deploy target is determined by environment variable or program argument. Also, if it was a remote table it could not be bypassed as easily.
It might be nice to optionally have some sort of guard rail or required confirmation step for production migrations. I typically use
ctrl+rto get my migrate command from my shell history. It is too easy to accidentally get and run the production migrate command when wanting to migrate development.It would be nice to have a confirmation step that required typing the name of the environment.
This could be toggled in the config files locally or with a special table remotely. Local config might be simpler, but it could be more difficult when deploy target is determined by environment variable or program argument. Also, if it was a remote table it could not be bypassed as easily.