Ensure versions are written to .env on undeploy #633

Closed
opened 2024-07-28 07:59:21 +00:00 by moritz · 1 comment
Member

As I understand it correctly from #625 at the moment the versions are only written on deploy/upgrade/rollback.
I think it's a good idea to check for some version conflicts on undeploy. If you have for some reason an outdated .env file the undeploy command should compare the currently deployed version and the version in the env file and warn the user if they differ and ask if the deployed version should be written into the .env file.

As I understand it correctly from #625 at the moment the versions are only written on deploy/upgrade/rollback. I think it's a good idea to check for some version conflicts on undeploy. If you have for some reason an outdated .env file the undeploy command should compare the currently deployed version and the version in the env file and warn the user if they differ and ask if the deployed version should be written into the .env file.
decentral1se added the
enhancement
abra
labels 2024-07-28 10:59:04 +00:00
Owner

abra app undeploy now writes the version it undeploys.

It doesn't handle the logic hinted at above but I'm gonna punt that into coop-cloud/organising#467 which is the final boss.

`abra app undeploy` now writes the version it undeploys. It doesn't handle the logic hinted at above but I'm gonna punt that into https://git.coopcloud.tech/coop-cloud/organising/issues/467 which is the final boss.
Sign in to join this conversation.
No description provided.