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
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
Most libraries and environments support loading secrets and sensitive data from a manager like AWS Secrets and 1Password to avoid storing this data in the repository.
However, because GOOGLE_APPLICATION_CREDENTIALS must be a file it cannot be used with 1Password to avoid checking in this sensitive data in the VCS.
Describe the solution you'd like
Allow CredentialsLoader to detect if a proper JSON (string) is loaded instead of just checking for a path.
Describe alternatives you've considered
Using CloudFlare rather than reCAPTCHA Enterprise.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
Most libraries and environments support loading secrets and sensitive data from a manager like AWS Secrets and 1Password to avoid storing this data in the repository.
However, because
GOOGLE_APPLICATION_CREDENTIALS
must be a file it cannot be used with 1Password to avoid checking in this sensitive data in the VCS.Describe the solution you'd like
Allow
CredentialsLoader
to detect if a proper JSON (string) is loaded instead of just checking for a path.Describe alternatives you've considered
Using CloudFlare rather than reCAPTCHA Enterprise.
Additional context
n/a
The text was updated successfully, but these errors were encountered: