Skip to content
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

Cloud Run deployment may not be able to access secrets #304

Open
ag-adampike opened this issue May 9, 2024 · 0 comments
Open

Cloud Run deployment may not be able to access secrets #304

ag-adampike opened this issue May 9, 2024 · 0 comments
Assignees
Labels
documentation For documentation-related issues

Comments

@ag-adampike
Copy link
Member

This step is expected to fail if the project for the deployment is not named op-scim-bridge.

5. Enable Cloud Run to access the secret using the Compute Engine default service account for the project:
```sh
gcloud secrets add-iam-policy-binding scimsession --member=serviceAccount:$(
gcloud iam service-accounts list --filter="$(
gcloud projects describe op-scim-bridge --format="value(projectNumber)"
)-compute@developer.gserviceaccount.com" --format="value(email)"
) --role=roles/secretmanager.secretAccessor
```

A known workaround is to replace op-scim-bridge with the project ID in this line when running the chained command in the code block:

gcloud projects describe op-scim-bridge --format="value(projectNumber)"

Discussion for suggested improvements in #292 (comment).

@ag-adampike ag-adampike added the documentation For documentation-related issues label May 9, 2024
@ag-adampike ag-adampike self-assigned this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation For documentation-related issues
Projects
None yet
Development

No branches or pull requests

1 participant