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

Deployment to GCS/S3 fails without credentials in .boto file #10

Closed
jeremydw opened this issue Mar 13, 2014 · 0 comments
Closed

Deployment to GCS/S3 fails without credentials in .boto file #10

jeremydw opened this issue Mar 13, 2014 · 0 comments
Labels
bug

Comments

@jeremydw
Copy link
Member

We should make it possible to interactively supply GCS/S3 credentials (just like Google's oauth2client) during deployment if they're not already available in the environment via a .boto file.
@jeremydw jeremydw added the bug label Mar 13, 2014
jeremydw added a commit that referenced this issue Oct 25, 2015
@jeremydw
Add support for the oauth2-dance flow for GCS deployments. Remove sup…
35e40f8 
…port for using local keys provided in podspec.yaml. Preserve support for boto-based authentication. Fixes #10.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremydw