Updated authentication section for clarity.

[jgeewax]

This change makes it very clear that if you're not running on GCE, keyfile.json is required, and this section explains how you find it.

[stephenplusplus]

What about "where do I get a JSON key file?" to match the phrasing of the last step in the same section:

If you want to generate a new key for an existing service account, click on Generate new JSON key and download the JSON key file.

The filename "keyfile.json" might be confusing, since the downloaded json file name is much longer.

[jgeewax]

Hmm I was trying to go for something that lined up with our sample code... Maybe we can tweak the sample too to look like:

// Or from elsewhere:
dataset = new datastore.Dataset({
  projectId: 'my-project',
  keyFilename: 'path to your JSON key file here'
});

?

[stephenplusplus]

Oh, I see. I think it's still clear with the "where do I get a JSON key file?" phrasing. "/path/to/keyfile.json" lets anyone know it's a JSON key file.

--edit--

The only reason I don't think it's as clear the other way around is we're using "keyfile.json" to match up with the example, but they haven't had a chance to read that yet. "keyfile.json" in that case sounds a little more like there's actually a json file named "keyfile.json" I need, where as in the case of "/path/to/keyfile.json" it's more obvious it's a made up file path.

And that will conclude today's over-thinking. I'm sure either will work just fine 👍

[aliafshar]

How about a single sample instead covering both cases?

dataset = new datastore.Dataset({
  projectId: 'my-project',

  // Not required on Google Compute Engine where we authorize for you.
  keyFilename: 'path to your JSON key file here'
});

[ryanseys]

How about explicitly just saying with/without GCE? [the demo codez are put inline here but I think they come after the instructions]

Authentication

Authenticating for gcloud-node is easy because...

With Google Compute Engine (GCE)

Authentication is handled automatically for you if your app is on GCE. Enable your APIs etc etc blah blah...

dataset = new datastore.Dataset({
  projectId: 'my-project'
  // You don't need a keyFilename on GCE :)
});

Without Google Compute Engine

1. Do this
2. Do that.
3. And this.

dataset = new datastore.Dataset({
  projectId: 'my-project',
  // Download your keyFilename on console.developers.google.com
  keyFilename: 'path to your JSON key file here'
});

[ryanseys]

🐴🔨

[jgeewax]

I'm a huge +1 to @ryanseys answer here... I'm going to see if we can tweak this a bit to fit without making the file too long.

I'd also like to show some screenshots of how to do this in the cloud console... It confused me several times. I don't want this to become a hugely long tutorial page, but we have to balance that with the "how fast can we get up to speed... Maybe for each product we should start thinking about a wiki page inside the GH repo ? or a README-Datastore.md specific file?

Here's an example of the screenshots I'd like to somehow include...

Show advanced options...

Enable the API's you want

(We can add an arrow pointing to "Enabled" on Cloud Datastore)

[silvolu]

What about:

• add an authentication page to the docs covering the topic more in detail (including the screenshots)
• leave only the example snippets with/without GCE on the readme and add links to the relevant sections in the auth docs

[rakyll]

+1 to @silvolu's suggestion.

I don't think we need separate auth guides for each service. It's not much fragmented.

[stephenplusplus]

add an authentication page to the docs covering the topic more in detail (including the screenshots)

This was more or less covered with our instantiation duality PR, which introduced a "Getting Started with gcloud" section atop every API page. Given the updates, how should we proceed with the ideas discussed here?

edit

I forgot what we were talking about here. nm. I'll get started on a docs auth page.

[jgeewax]

I'm going to close this out as we probably need to make a couple other decisions first. The goal was to have this done for the blog post, but I suspect it's not such a big deal as of now.

Thanks for the comments.