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

Storage Backend: Google Cloud Storage #211

Closed
e2b opened this issue Jul 4, 2015 · 4 comments
Closed

Storage Backend: Google Cloud Storage #211

e2b opened this issue Jul 4, 2015 · 4 comments

Comments

@e2b
Copy link

e2b commented Jul 4, 2015

Google's Cloud Storage Nearline has a pricing similar to Amazon Glacier, but with ~3 sec response times and free ingress (upload) traffic.

@fd0 fd0 added type: feature enhancement improving existing features category: backend feature and removed type: feature enhancement improving existing features labels Jul 4, 2015
@kurin
Copy link
Contributor

kurin commented Sep 15, 2015

I'd like to add this feature. I'll send a pull request in a few days.

@fd0
Copy link
Member

fd0 commented Sep 16, 2015

Cool, please go ahead! 👍

ckemper67 added a commit to ckemper67/restic that referenced this issue May 14, 2016
…g s3 support

to address restic#211.

Added a new package to handle GCS configuration. GCS repositories get specified
using gs://bucketname/prefix syntax, similar to gsutil.

Added tests for the various cases to config_test and location_test.
ckemper67 added a commit to ckemper67/restic that referenced this issue Jul 31, 2016
…g s3 support

to address restic#211.

Added a new package to handle GCS configuration. GCS repositories get specified
using gs://bucketname/prefix syntax, similar to gsutil.

Added tests for the various cases to config_test and location_test.
ckemper67 added a commit to ckemper67/restic that referenced this issue Dec 30, 2016
…g s3 support

to address restic#211.

Added a new package to handle GCS configuration. GCS repositories get specified
using gs://bucketname/prefix syntax, similar to gsutil.

Added tests for the various cases to config_test and location_test.
@fd0
Copy link
Member

fd0 commented Jan 23, 2017

As just said in the PR #449: I'd like to move forward with adding GCS backend support natively. What is needed in order to access it? A client ID or a client secret?

@fd0
Copy link
Member

fd0 commented Feb 12, 2017

According to @gebi, no such thing is needed, so that's good news.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants