-
Notifications
You must be signed in to change notification settings - Fork 24
Make it easier to use non defaults CredentialsProvider #472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Guillaume, Trying to figure out how to prioritize this: Are you unable to use default credentials either through GOOGLE_APPLICATION_CREDENTIALS or machine defaults on Compute Engine? If so, why? If we implemented this, we'd probably want to do it across other languages as well. -Dan |
Do facilitate our migration to GCP, we will need to be able to publish messages to Pub/Sub from our data center. In our infrastructure, the local filesystem can't be considered secure . For other GCP client, we simply base64 the credential file and put he result as an environment variable. Creating a CredentialsProvider from that is pretty trivial. In addition, we have used impersonated credentials from time to time. |
Thank you for the scope as to why this is necessary. I'll ensure this is implemented in all clients. |
These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472
These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472
These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472
) * feat: Add CredentialsProvider to Publisher and Subscriber settings These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472 * feat: Add CredentialsProvider to Publisher and Subscriber settings These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472 * feat: Add CredentialsProvider to Publisher and Subscriber settings These objects require more than one client and are annoying to construct correctly. Add a commonly needed setting to the top level here. Fixes #472 * fix: clirr * fix: flaky test * fix: deps * fix: scopes * fix: format * fix: dependencies again * fix: admin endpoint
Is your feature request related to a problem? Please describe.
To be able to set a CredentialsProvider on a SubscriberSettings, you need to set the credentials on a
Supplier<SubscriberServiceClient>
, aSupplier<CursorServiceClient>
and aPartitionAssignmentServiceClient
Describe the solution you'd like
Be able to set
CredentialsProvider
on theSubscriberSettings
directly.The text was updated successfully, but these errors were encountered: