-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
Google Cloud Storage Support (Storage backends) #685
Comments
It would be nice to have, can you implement it? |
boto is ok for aw services, but for more generic cloud (storage) interaction, I'd look into pyrax to build on, a python-cloudfiles replacement. |
boto is an optional dependency, it is fine to add backends based on other optional libraries. does pyrax support Google Cloud Storage? it looks like a openstack only thing. |
I haven't tried, since I'm not using google's stuff, but I thought it should - it's s3-compat from what I can see, though I understand there are small differences between s3 and swift api implementations. I was seeing pyrax as the most generic solution here since openstack's becoming the baseline tools api, but if I'm wrong, libcloud looks good as well and seems to support google c.s. That way it wouldn't be a google-only backend here, but hopefully useable with many object storage providers, like rackspace cloud, ovh hubic (cloudfiles-version), and of course all openstack swift users, maybe riak and more. |
I would like to try to implement it but I don't think I have the skills to do that on my own. |
I implemented this feature. Please check my PR 🙏 |
[MRG+2] Fixes #685 FilesPipeline support for Google Cloud Storage.
I think we could reopen this issue. The GCS support was added only as a File Store and not as a Feed Storage. |
I implemented the GCS feed export in this PR. Please note, it is a work in progress at this moment. |
[MRG+1] Fix for #685 Add Google Cloud Storage Feed Export
Does it make sense to support Google Cloud Storage as storage backend? Boto already supports Cloud storage: http://boto.readthedocs.org/en/latest/ref/gs.html
The text was updated successfully, but these errors were encountered: