rm
doesn't clean up config
#577
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?
I've created an app using
abra app new ..
then removed it usingabra app rm ...
butdocker config ls
on the server shows the configs from this app are not cleaned upOne thing that could be the reason, the recipe had a config during the creation that wasn't there during the cleanup, perhaps some sort of an error silently happened during the rm process
I believe the compose configs are merged to discover configs/secrets/etc. and then things are deleted. So, if you change your config, yes, you can disrupt what will be deleted. We could implement a more thorough cleanup searching for configs/secrets/volumes/etc. matching the convention? I'm not sure if this would have unintended consequences.