Skip to content
This repository was archived by the owner on Mar 11, 2026. It is now read-only.
This repository was archived by the owner on Mar 11, 2026. It is now read-only.

1.1.2 breaks logging when using default credentials #53

@imathews

Description

@imathews

Environment details

  • OS: GKE, kubernetes 1.8.6
  • Node.js version: 8.6
  • @google-cloud/logging version: 1.1.2

Steps to reproduce

When upgrading from 1.1.1 to 1.1.2, logging no longer works in our staging / prod environments — I don't see any of the logs in the Stackdriver interface, but otherwise it fails silently, with no corresponding errors, etc. I can confirm that reverting to 1.1.1, without changing anything else, remedies the problem.

Interestingly, this all behaves fine on 1.1.2 in our dev environment (we still send logs to stackdriver for testing purposes). The only difference between dev and staging / prod is that we're using a keyfile in dev, while we rely on the default credentials within the nodes of our GKE cluster to authenticate in the other environments.

Let me know if I can provide any additional info to help troubleshoot, and many thanks in advance.

Metadata

Metadata

Labels

🚨This issue needs some love.api: loggingIssues related to the googleapis/nodejs-logging API.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions