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
{{ message }}
Repository navigation
Allow users to specify p12/json credentials file #638
What is the process to specify the keyfile path? That is, I know my keys are at "/creds.json" or "/key.p12" (pick whichever you want) and don't want to use the environment variable stuff...
We need to make sure that people can still be explicit. So the goal of this bug is to make sure people can specify a path to either a .p12 file or a .json file with credentials, and use all the services with those credentials...
Activity
Adding get_for_service_account_json function in credentials.
build(deps): bump requests to 2.31.0 [autoapprove] (#638)
feat: migrating off of circle/ci (#638)
chore(main): release 2.11.3 (#638)
feat: add google.api_core.version_header (#638)
CI: add flaky to exactly-once sample test and add a non-regional test (…
fix: add DECIMAL and BIGDECIMAL as aliases for NUMERIC and BIGNUMERIC (…
chore: release 2.15.0 (#637)
refactor: update coverage score in nox file and cleanup imports in te…
bug: Support Retrieval of Cross-Schema Foreign Keys (#681)
chore(python): omit google/__init__.py in coverage (#638)
chore(python): add comment in .kokoro/docs/common.cfg for Cloud RAD (#…