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 }}
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.
I'm using service accounts set up and linked as per the documentation.
Setting the environment variable SECRETHUB_IDENTITY_PROVIDER=gcp, the python API works as expected inside containers running on GCP, e.g. in Cloud Run, under this service account.
I would like to access secrets inside serverless functions with python. Running the following in a Python 3.8 Google Cloud Function results in a hang and timeout:
import secrethub
client = secrethub.Client()
I have the appropriate service account and environment variable set on the Cloud Function. Egress is allowed to the internet. The secrethub package version is 0.1.1. Any tips would be appreciated (or even if someone could reproduce this), thanks!
The text was updated successfully, but these errors were encountered:
I've pinpointed the problem to a specific function in the GCP SDK and am now investigating why this function hangs for Python Cloud functions functions specifically. I will let you know as soon as I find a solution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using service accounts set up and linked as per the documentation.
Setting the environment variable
SECRETHUB_IDENTITY_PROVIDER=gcp
, the python API works as expected inside containers running on GCP, e.g. in Cloud Run, under this service account.I would like to access secrets inside serverless functions with python. Running the following in a Python 3.8 Google Cloud Function results in a hang and timeout:
I have the appropriate service account and environment variable set on the Cloud Function. Egress is allowed to the internet. The
secrethub
package version is 0.1.1. Any tips would be appreciated (or even if someone could reproduce this), thanks!The text was updated successfully, but these errors were encountered: