Lego: DNS provider for Google Cloud should accept credentials

Created on 10 Jun 2016 · 5Comments · Source: go-acme/lego

The current implementation of the Google Cloud DNS provider only works if a node, where lego is deployed, has node metadata available. However, that's not always possible. So it should also accept CLIENT_ID and CLIENT_SECRET pair for such cases.

Source

kop

👍1

Most helpful comment

You can also provide the GOOGLE_APPLICATION_CREDENTIALS env var and have it point to a json credentials file. That's probably what you want ?

luna-duclos on 18 Aug 2016

👍3

All 5 comments

You don't necessarily need node metadata. It also works if gcloud is installed and authenticated.

peterwald on 8 Jul 2016

You can also provide the GOOGLE_APPLICATION_CREDENTIALS env var and have it point to a json credentials file. That's probably what you want ?

luna-duclos on 18 Aug 2016

👍3

@PSG-Luna, yes this solves the problem.

kop on 18 Aug 2016

I'll go ahead and close this then. :)

xenolf on 23 Aug 2016

Is this documented anywhere?
I exported GOOGLE_APPLICATION_CREDENTIALS previously for my Cloud SQL Service Account limited to roles/cloudsql.client -- took me a day to figure out why my API calls where coming back 403 Forbidden

Just obtained my certs now though, so thank yous all around 😄 !