Create gcloud-node client that uses metadata service auth

[drewbryant]

How can I force the gcloud-node client to attempt to use the compute engine environment, which relies upon the "metadata service" for getting auth tokens?

I see this chunk of code in lib/storage/index.js, and I don't see where/how it is checking for the compute engine environment:

function Storage(config) {
  if (!(this instanceof Storage)) {
    return new Storage(config);
  }

  this.makeAuthorizedRequest_ = util.makeAuthorizedRequest({
    credentials: config.credentials,
    keyFile: config.keyFilename,
    scopes: SCOPES
  });

  this.projectId = config.projectId;
}

Basically I'm attempting to create my client like this:

var gcloud = require('gcloud');
var storage = gcloud.storage();

And I'm hitting an error because I haven't passed a config object with credentials. The docs here made it seem like this was the expected syntax on compute engine however (i.e., gcloud.storage()).

Is this auth approach supported currently?

[stephenplusplus]

Can you try with master? We recently went through an overhaul of how we authenticate, but it hasn't had a release yet.

[drewbryant]

Thanks Stephen, it looks like the version in master is working on GCE with the metadata auth approach.

Follow-up question:
How have you been testing the GCE support locally (i.e., outside of GCE)? Do you simulate the GCE metadata service?

[stephenplusplus]

For my testing, I actually pushed to a GCE endpoint. But fortunately, with our upcoming release, we have removed most of our auth code and instead use the google-auth-library. They have many unit tests that make sure the right requests are made for auth tokens and such.

I'm glad to hear master solves the problem, and sorry for the confusion with the current release. We should be getting a new release out soon.