Prompt to prevent potential database disaster? #322

New Issue

decentral1se · 2022-05-16T14:42:37Z

decentral1se commented

2022-05-16 14:42:37 +00:00

We ran into an issue where a new version of a DB was deployed and then it did some upgrade work on the internals in the background. Then someone deployed an older version of that DB and it exploded complaining that a newer version of the database had done work and now you can't run the old.

We could guard against this:

if recipe has a db service
if recipe is deployed, and app is up
if deployed version is $x & new version to be deployed is < $x
prompt to ask if this is what you want?

Especially for anything mariadb/mysql 😱

We ran into an issue where a new version of a DB was deployed and then it did some upgrade work on the internals in the background. Then someone deployed an older version of that DB and it exploded complaining that a newer version of the database had done work and now you can't run the old. We could guard against this: - if recipe has a `db` service - if recipe is deployed, and app is up - if deployed version is `$x` & new version to be deployed is < `$x` - prompt to ask if this is what you want? Especially for anything mariadb/mysql 😱

decentral1se added the

enhancement

abra

labels 2022-05-16 14:42:37 +00:00

3wordchant commented

2022-05-16 15:08:46 +00:00

For our future selves, this was wordpress, I think i remember similar bullshit with nextcloud also.

Sign in to join this conversation.