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.

Sign up for GitHub

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

Jump to bottom

[Documentation Issue] Include doc for exclusion of GCE credentials for generate_signed_url #983

Closed
julienmarcbrown opened this issue Jul 13, 2015 · 3 comments
Closed

[Documentation Issue] Include doc for exclusion of GCE credentials for generate_signed_url #983

julienmarcbrown opened this issue Jul 13, 2015 · 3 comments
Assignees
@dhermes
Labels
api: storage Issues related to the Cloud Storage API.

Comments

@julienmarcbrown
Copy link

Page Name: storage-blobs
Release: 0.6.0

Since generate_signed_url parameter 'credentials' isn't supported currently by GCE, should include notice.
@dhermes
Copy link
Contributor

dhermes commented Jul 13, 2015

Good call. Thanks! Related to #922

@julienmarcbrown
Copy link
Author

any idea of a workaround? or if it will be supported in the future?

@dhermes
Copy link
Contributor

dhermes commented Jul 13, 2015

Can you chime in on #922? I don't have visibility into internal feature development at Google. You can support it today by just using a service account via a JSON key file on GCE. Put it in your VM image or as a metadata value.

dhermes added a commit to dhermes/google-cloud-python that referenced this issue Jul 14, 2015
@dhermes
Documenting exclusion of GCE for generate_signed_url.
98a8d19 
Fixes googleapis#983.
@dhermes dhermes mentioned this issue Jul 14, 2015
Merged
@dhermes dhermes added docs api: storage Issues related to the Cloud Storage API. labels Dec 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dhermes dhermes

Labels
api: storage Issues related to the Cloud Storage API.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dhermes @julienmarcbrown