Add credential configuration file support to Google Secrets Manager secrets backend #31597
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…anager secrets backend
boring-cyborg
bot
added
area:providers
area:secrets
kind:documentation
provider:google
uranusjr
approved these changes
May 30, 2023
potiuk
approved these changes
May 30, 2023
86 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds a
gcp_credential_config_filebackend_kwargsoption to Google Secrets Manager's secret backend implementation that allows the secrets backend to authenticate to the secrets manager service using a credential configuration file. This is usually used to support workload identity federation use cases by providing external credentials, but it also supports a wide range of credential types:authorized_userservice_accountexternal_accountexternal_account_authorized_userimpersonated_service_accountgdch_service_accountThis is a follow-up PR to #31548.