Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete stack from state #790

Open
project0 opened this issue Jan 16, 2025 · 1 comment
Open

Delete stack from state #790

project0 opened this issue Jan 16, 2025 · 1 comment
Labels
kind/enhancement Improvements or new features

Comments

@project0
Copy link

project0 commented Jan 16, 2025

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I am using the s3 backend and noticed that states are not entirely cleaned up after deleting a stack:

The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained.
If you want to remove the stack completely, run pulumi stack rm main-flowers-dev-environments-shared.

It would be great to have an option to trigger the stack deletion as part of the operator. I am using it to create ephemeral environments and it results into a lot of "empty" states in my s3 bucket :-(.

Affected area/feature

@project0 project0 added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Jan 16, 2025
@EronWright
Copy link
Contributor

It is a reasonable request, and I suppose this would best be done via a new "stack retention policy" flag.

@EronWright EronWright removed the needs-triage Needs attention from the triage team label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants