fix: do not try and authenticate when error reporting is disabled#676
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
@losalex anything additional needed from me to get the tests going and eventual merge/release? I think because I'm first time I might need someone to kick those off for me |
Thanks @comp615 for making this change! Added a comment - basically you need to add additional config parameter controlling this feature and add all relevant tests to make sure that this flag by default does not impacts existing code and also does not introduces new failures. Also - did you run this change locally and tested E2E with GCP? |
eef1da0 to
44c42f2
Compare
losalex
left a comment
There was a problem hiding this comment.
LGTM - please run this change in GCP E2E with getShouldReportErrorsToAPI on/off to make sure it works as expected
We've been running this E2E since last week and have not observed any new errors on either side of the boolean. That value is off/false in our test/development environments and on in our production environments. |
losalex
left a comment
There was a problem hiding this comment.
Seems there are bunch of system tests failing - see https://source.cloud.google.com/results/invocations/b2b15578-b54f-4360-8620-bbc5fece441b/targets/cloud-devrel%2Fclient-libraries%2Fnodejs%2Fpresubmit%2Fgoogleapis%2Fnodejs-error-reporting%2Fnode12%2Fsystem-test/log
|
Try that new build. I'm really struggling to get the last few error-reporting tests running locally, so kind of guessing at what the tests need if anything. Would be much easier to debug in CI :-/ |
Fixes #550