Ensure versions are written to .env on undeploy #633
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 referenced this issue2024-12-21 19:28:13 +00:00
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.