-
Notifications
You must be signed in to change notification settings - Fork 29
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
Object storage integration (set of object versions) #461
Comments
Thoughts:
|
Agreed. You'll be able to add an s3 remote ( |
An S3 remote is probably a set of S3 API credentials; then when we do |
Plan:
Server side:
|
also use them to check we can access S3 and have buckets to talk to.
It would be nice to not need this or be able to unmarshal to dmremotes then save the config file as dmremotes not remotes...
Idea not for right now: we're specifying that you can't switch to an s3 remote to avoid extra overhead/feature creep/etc, but it'd be quite easy to |
Testing thoughts: But many of them explicitly state they don't support versioning which might be a problem. |
Some other random thoughts:
|
…k we can't push again before committing something new
Left to do:
|
Hacking my way through subsets at the moment. I think there may be some complications with push/pull - if a user clones a part of an S3 bucket, then pushes the changes to S3, this will delete the files we ignored when we cloned it. Similarly, if a user clones then pulls an S3 bucket, we will inadvertently get all of the files when the user requested only a part of them initially. What I'm thinking is where we have We may need to think about an override to this, though, such as |
Design document:
https://docs.google.com/document/d/1VFigteB-8QTmNpIIobfPYnu8R9pnKW_zHazA_NAdwM0/edit
The text was updated successfully, but these errors were encountered: