You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we ship our software, call it Acme Inc., through container images, that connect to external PG instances.
How can we work with the following scenario:
Users use Acme_Inc@v0.0.1
Migrations are executed on container init
Users spin up new container Acme_Inc@0.0.2
Migrations are applied
Something breaks in the logic and they decide to re-use Acme_Inc@0.0.1
Does the CLI knows that the migrations now should perform a down operation? Or are we responsible to perform this? If so, how would you recommend approaching this?
I tried to find something in the docs, but the only thing I could find was that you just keep track for versions used.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey folks,
Currently we ship our software, call it
Acme Inc.
, through container images, that connect to external PG instances.How can we work with the following scenario:
Acme_Inc@v0.0.1
Acme_Inc@0.0.2
Acme_Inc@0.0.1
Does the CLI knows that the migrations now should perform a
down
operation? Or are we responsible to perform this? If so, how would you recommend approaching this?I tried to find something in the docs, but the only thing I could find was that you just keep track for versions used.
Beta Was this translation helpful? Give feedback.
All reactions