Skip to content

[fix][googlecloudmonitoringreceiver]: remove creds check#36648

Merged
codeboten merged 1 commit into
open-telemetry:mainfrom
VihasMakwana:googlecloud-fix
Dec 4, 2024
Merged

[fix][googlecloudmonitoringreceiver]: remove creds check#36648
codeboten merged 1 commit into
open-telemetry:mainfrom
VihasMakwana:googlecloud-fix

Conversation

@VihasMakwana
Copy link
Copy Markdown
Contributor

Description

Fix "no validation found" error if workload is running on Google Cloud Platform.
There's no need to check for creds or creds.JSON explicitly. If any errors are encountered, it will be thrown by FindDefaultCredentials.

Link to tracking issue

Fixes #36607

@dashpole dashpole added the ready to merge Code review completed; ready to merge by maintainers label Dec 3, 2024
@codeboten codeboten merged commit a54f970 into open-telemetry:main Dec 4, 2024
@github-actions github-actions Bot added this to the next release milestone Dec 4, 2024
shivanthzen pushed a commit to shivanthzen/opentelemetry-collector-contrib that referenced this pull request Dec 5, 2024
…try#36648)

#### Description
Fix "no validation found" error if workload is running on Google Cloud
Platform.
There's no need to check for `creds` or `creds.JSON` explicitly. If any
errors are encountered, it will be thrown by `FindDefaultCredentials`.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#36607
ZenoCC-Peng pushed a commit to ZenoCC-Peng/opentelemetry-collector-contrib that referenced this pull request Dec 6, 2024
…try#36648)

#### Description
Fix "no validation found" error if workload is running on Google Cloud
Platform.
There's no need to check for `creds` or `creds.JSON` explicitly. If any
errors are encountered, it will be thrown by `FindDefaultCredentials`.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#36607
sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this pull request Dec 17, 2024
…try#36648)

#### Description
Fix "no validation found" error if workload is running on Google Cloud
Platform.
There's no need to check for `creds` or `creds.JSON` explicitly. If any
errors are encountered, it will be thrown by `FindDefaultCredentials`.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#36607
AkhigbeEromo pushed a commit to sematext/opentelemetry-collector-contrib that referenced this pull request Jan 13, 2025
…try#36648)

#### Description
Fix "no validation found" error if workload is running on Google Cloud
Platform.
There's no need to check for `creds` or `creds.JSON` explicitly. If any
errors are encountered, it will be thrown by `FindDefaultCredentials`.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#36607
zeck-ops pushed a commit to zeck-ops/opentelemetry-collector-contrib that referenced this pull request Apr 23, 2025
…try#36648)

#### Description
Fix "no validation found" error if workload is running on Google Cloud
Platform.
There's no need to check for `creds` or `creds.JSON` explicitly. If any
errors are encountered, it will be thrown by `FindDefaultCredentials`.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#36607
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Code review completed; ready to merge by maintainers receiver/googlecloudmonitoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

googlecloudmonitoringreceiver gives no valid credentials found Error

5 participants