fix: Correctly determine project ID for metrics export #2427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2420
This PR addresses an issue where the project ID for metrics export was not being correctly determined when not explicitly provided.
Specifically, this PR introduces the following changes:
Infers Project ID from Credentials: When a Spanner instance is created without a projectId in the spanner options, the project ID is now fetched from the authentication credentials. This ensures that metrics are correctly exported to the appropriate project, resolving an issue where a placeholder {{project_id}} was being used.
This PR also makes the
projectId
attribute to be non-optional inMetricsTracerFactory.getInstance
method