You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Quarkus Google Cloud Services extension pack contains GraalVM substitutions for gRCP and Google Cloud Auth support.
It is already used by the Micrometer Google Cloud exporter, it could also be used by the Opentelemetry Google Cloud exported provided in this extension.
It would avoid having duplicate substitution and possibly having native configuration on multiple modules that may be in conflict.
Note that Google Cloud have native support that may be use instead of providing our own, I still have on my todo list to upstream the substitution on our side.
We can discuss this on Zulip if needed.
The text was updated successfully, but these errors were encountered:
t0xa
added a commit
to t0xa/quarkus-opentelemetry-exporter
that referenced
this issue
Apr 14, 2023
I've compared substitutions defined in quarkus-google-cloud-services gRCP common and in the current version. The only difference is the usage of mtls Channel Credentials (see below). I've tried to move this logic into quarkus-google-cloud-services gRCP common locally but it still gives me an error.
As far as I remember the difference for between the two substitutions is around automatic auth for AppEngine, as AppEngine didn't support native image I just disable its auth.
Hi,
The Quarkus Google Cloud Services extension pack contains GraalVM substitutions for gRCP and Google Cloud Auth support.
It is already used by the Micrometer Google Cloud exporter, it could also be used by the Opentelemetry Google Cloud exported provided in this extension.
The substitution are here: https://github.com/quarkiverse/quarkus-google-cloud-services/blob/main/common/grpc/src/main/java/io/quarkiverse/googlecloudservices/common/grpc/runtime/graal/GoogleApiGaxGrpcSubstitutions.java
It would avoid having duplicate substitution and possibly having native configuration on multiple modules that may be in conflict.
Note that Google Cloud have native support that may be use instead of providing our own, I still have on my todo list to upstream the substitution on our side.
We can discuss this on Zulip if needed.
The text was updated successfully, but these errors were encountered: