[GCP Logging] GCP project id from quarkus config is not considered #770
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.
The
quarkus.google.cloud.project-id
config property is not considered when using LoggingOptions default instance.I got the following stacktrace even though I specified the
quarkus.google.cloud.project-id
config property and even tried to useQUARKUS_GOOGLE_CLOUD_PROJECT_ID
as env variable:The problem is that
LoggingOptions.getDefaultInstance()
is already trying to find a project id in various ways (but not consideringquarkus.google.cloud.project-id
) and if that fails the call to the inheritedServiceOptions
constructor will raise anIllegalArgumentException
due to this:So in my case the
builder.projectId
is null and therefore theIllegalArgumentException
is thrown.I resolved the issue on my side by adding
GOOGLE_CLOUD_PROJECT=my-gcp-project-id
as system environment variable, but IMHO yourGcpBootstrapConfiguration
, akaquarkus.google.cloud.project-id
config property, should also be considered here ;)