-
Notifications
You must be signed in to change notification settings - Fork 268
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
spaces lifecycle policy not working as expected #752
Comments
I confirm this issue! same behavior |
Can you open a DigitalOcean support ticket so the team can take a closer look? If |
I suppose you are right, I'll reach them after some additional tests. |
Hello @baznikin, have we been able to resolve this issue for you? |
Hello @ChiefMateStarbuck!
|
So lifecycle policy doesn't support versioning on the bucket being set to Suspended. If I create a new Space bucket via the Digital Ocean portal 'aws s3api get-bucket-versioning' returns nothing. If I create a new Space bucket with Terraform using the latest Digital Ocean provider and set versioning to disabled, it creates a bucket that when queried returns versioning status as Suspended. If I create a new Space bucket with Terraform using the latest Digital Ocean provider and don't have anything specifying 'versioning' at all, then get-bucket-versioning returns nothing. I would have thought that setting versioning to disabled would have not configured any versioning at all. I guess I have to modify my Terraform module to workaround this. And also test to confirm that lifecycle option works with zero versioning config set (which I assume it does given it works for other people). |
Bug Report
Describe the bug
I try to set up lifecycle policy which should expire and delete files after one day. The rule is applied according to s3cmd, however, files are not deleted, they remain inside the space.
Affected Resource(s)
Expected Behavior
Files should be deleted after one day
Actual Behavior
Files remain inside the bucked
Steps to Reproduce
terraform apply
-->Terraform Configuration Files
Expected behavior
Additional context
s3cmd output of
s3cmd getlifecycle
The text was updated successfully, but these errors were encountered: