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
[Enhancement]: aws_s3_object delete by version #37446
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/s3
Issues and PRs that pertain to the s3 service.
Comments
Kiollpt
added
the
enhancement
Requests to existing resources that expand the functionality or scope.
label
May 11, 2024
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
terraform-aws-provider
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
May 11, 2024
justinretzolk
added
service/s3
Issues and PRs that pertain to the s3 service.
and removed
needs-triage
Waiting for first response or review from a maintainer.
labels
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/s3
Issues and PRs that pertain to the s3 service.
Description
There is a scenario where two workspaces reference the same object key, invoking the destroy operation under one of the workspaces results in the permanent deletion of the object.
However, in the case of a versioning-enabled bucket, I would prefer to delete the object with the version created by the workspace instead of being deleted permanently."
Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: