You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: make environment variables compatible with google-cloud-ruby #1852
It would be nice if node and ruby applications can use the same configuration environment variables, and same preceding logic. In my particular project I'm using two variables: DATASTORE_EMULATOR_HOST and GCLOUD_KEYFILE_JSON. First have higher priority. If it is unset, datastore client goes to service endpoint specified by content of GCLOUD_KEYFILE_JSON. For node application I need to implement it myself
We do support the datastore emulator variable, and for JSON, try GOOGLE_APPLICATION_CREDENTIALS, which comes from when you authenticate using the gcloud SDK, but you can set the env var manually to point to a JSON key file. That should be supported in Ruby as well.
Activity
stephenplusplus commentedon Dec 2, 2016
We do support the datastore emulator variable, and for JSON, try
GOOGLE_APPLICATION_CREDENTIALS, which comes from when you authenticate using the gcloud SDK, but you can set the env var manually to point to a JSON key file. That should be supported in Ruby as well.stephenplusplus commentedon Dec 2, 2016
Going to close @timanovsky, but let me know if
GOOGLE_APPLICATION_CREDENTIALSdoesn't do the trick.lukewlms commentedon Jun 27, 2018
There's a solution here for using environment variables instead of an on-disk file (critical for our Heroku setup).
You can authenticate with
credentials: { private_key, client_email }rather than path to a json file.fix(deps): update dependency @opentelemetry/semantic-conventions to ~…
chore(main): release 4.0.7 (#1850)
chore(main): release 4.0.7 (#1850)