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

Manage S3 object versions #22828

Closed
YakDriver opened this issue Jan 28, 2022 · 2 comments
Closed

Manage S3 object versions #22828

YakDriver opened this issue Jan 28, 2022 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@YakDriver
Copy link
Member

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Is there interest in managing a specific version of an S3 object?

Currently, s3_object refers to the latest version of an object. However, it might be useful to manage versions other than the latest.

This could be accomplished two ways:

  • with a new resource s3_object_version or
  • by adding to the s3_object resource.

How do we want this to work in practice? If you're managing a non-latest version, it implies that the object already exists so you'd be importing a resource into Terraform management or otherwise referring to an existent resource. You cannot specify a version ID when creating an object but you can when getting an object. For this reason, it seems like adding the ability to import a specific version using s3_object may be the best approach.

Please share if you have other ideas.

New or Affected Resource(s)

  • aws_s3_object
  • aws_s3_object_version (?)

References

@YakDriver YakDriver added the enhancement Requests to existing resources that expand the functionality or scope. label Jan 28, 2022
@github-actions github-actions bot added the service/s3 Issues and PRs that pertain to the s3 service. label Jan 28, 2022
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jan 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2024
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

1 participant