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

a wrong explanation in [GOOGLE COMPUTE BUILDER] #1669

Closed
BS-BAE opened this issue Nov 11, 2014 · 2 comments
Closed

a wrong explanation in [GOOGLE COMPUTE BUILDER] #1669

BS-BAE opened this issue Nov 11, 2014 · 2 comments
Assignees

Comments

@BS-BAE
Copy link

BS-BAE commented Nov 11, 2014

Hi,

I'd tried to build an image of GC with packer and followed a document GOOGLE COMPUTE BUILDER (http://www.packer.io/docs/builders/googlecompute.html).

This document explain that in order to build GC's image user has to download json formatted account_file and client_secrets_file from GC and put paths of these files in script. and kindly explain how to download these files.

However Unfortunately, In this document, there was an incorrect step to get an account file. it describes that when creating a new OAuth of GC, user can download a json formatted account file. But the file wasn't json but p12 authentication file.

In fact, user actually just need to put the client_secrets_file instead of account_file. The client_secrets_file includes entire information of account_file.

Thus, please fix the document to prevent user to download and use wrong file (*.p12) or change API not to use account_file parameters.

Best regards
Bae

@sparkprime
Copy link
Contributor

In the Google Cloud Platform console, credentials section, you can download either a JSON or a P12 file containing keys for a given service account. The "Generate new JSON key" button will both generate a new key (added to the existing keys) and automatically download it in your browser. Same for the "Generate new P12 key" button.

@erjohnso
Copy link
Contributor

Hi @BS-BAE - just merged #1679 which updates auth mechanisms and cleans up the docs consistent with @sparkprime's comment. I believe this will address the confusing docs.

I'm assuming this covers the issue and am closing it out. Update the issue if you disagree.

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants