-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pure AWS S3 backend #5
Comments
|
Setback: an S3 object can only have up to 10 tags. Poses a problem if a target is part of more than 10 snapshots, which is likely to come up for almost all projects. |
Another idea: the metadata already has hashes, which is half the battle for a key-value store. Snapshot
Checkout
Hopefully (2) will be possible without cloning a bunch of infrastructure from StatusGit status of |
Closing in favor of ropensci/targets#711 |
Reopening. Relative to native AWS versioning in targets, an AWS gittargets backend would allow less frequent uploads and allow users to opt in later in the project’s life cycle. |
On reflection: if you're already using AWS S3, then https://books.ropensci.org/targets/cloud-storage.html is way better. |
Prework
Proposal
Similar to #2, but directly implemented on top of AWS S3 through something like
aws.s3
,paws
, orbotor
. Use the historical versioning and tagging capabilities of buckets.The text was updated successfully, but these errors were encountered: