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

Add lifecycle configuration to delete objects under a certain size to remove destroyed states #147

Open
nitrocode opened this issue Oct 13, 2023 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@nitrocode
Copy link
Member

Describe the Feature

It's nice to look at the s3 state bucket to see which components and root dirs contain resources

After destroying root components and resources, the state file object continues to exist in s3. The state object has very few characters in there. It would be nice to expire these objects when they are less than a certain number of bytes.

Expected Behavior

Expire s3 state objects when the objects are less than N bytes

Use Case

See above

Describe Ideal Solution

Lifecycle rule

Alternatives Considered

N/A

Additional Context

@Gowiem Gowiem added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jul 4, 2024
@Gowiem
Copy link
Member

Gowiem commented Jul 4, 2024

It's kinda sketchy to do this, but I would like to see it if it's possible... We do enable versioning by default, right? So that should give us some confidence that this won't just outright destroy state that is actually being used. That said, I could see this being a problem... added some labels to see if anyone wants to implement and then we can discuss more once it's in a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants