Pulumi doesn't remove stack from S3 bucket #639
Description
I store state in a S3 bucket and I noticed that all old data is staying there, e.g. now my bucket has 273 directories and at least one of them belongs to a crashed pipeline and I have no idea which one. I noticed messages like these in mapt logs which are probably related to this (notice 2 different stacks):
INFO The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained.
INFO If you want to remove the stack completely, run `pulumi stack rm stackRHELBaremetal-mapt-rhel-test-rhaiis-podman-cuda-x86-64-ml8wb`.
INFO The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained.
INFO If you want to remove the stack completely, run `pulumi stack rm spotOption-mapt-rhel-test-rhaiis-podman-cuda-x86-64-ml8wb`.
While I would like all data removed from S3 bucket, some users might want to keep it. IMHO mapt could have a parameter for setting this behavior.
Metadata
Metadata
Assignees
Labels
No labels