Skip to content

Commit 900d5ce

Browse files
Update docs/tutorials/deploying-from-github-actions/to-gcp.mdx
Co-authored-by: Eric Liu <[email protected]>
1 parent 71a4dec commit 900d5ce

File tree

1 file changed

+1
-1
lines changed
  • docs/tutorials/deploying-from-github-actions

1 file changed

+1
-1
lines changed

docs/tutorials/deploying-from-github-actions/to-gcp.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This tutorial will show you how to use the [Defang GitHub Action](https://github
1313
- [A Github Repo](https://docs.github.com/en/get-started/quickstart/create-a-repo)
1414
- [A GCP Account](https://cloud.google.com)
1515

16-
The following steps will guide you through setting up a GitHub Actions workflow that can assume a role in your GCP account using OpenID Connect (OIDC) and deploy your project using the Defang GitHub Action. The role which will be assumed must have a trust relationship with an OIDC identity provider (IdP) for GitHub Actions, and that trust relationship must be configured to allow the specific repository and branch to assume the role. This ultimately allows the GitHub Actions workflow to securely access your GCP resources without needing to store long-lived GCP credentials in your repository.AWS
16+
The following steps will guide you through setting up a GitHub Actions workflow that can assume a role in your GCP account using OpenID Connect (OIDC) and deploy your project using the Defang GitHub Action. The role which will be assumed must have a trust relationship with an OIDC identity provider (IdP) for GitHub Actions, and that trust relationship must be configured to allow the specific repository and branch to assume the role. This ultimately allows the GitHub Actions workflow to securely access your GCP resources without needing to store long-lived GCP credentials in your repository.
1717

1818
## Step 1 - Identify your GCP Project ID
1919

0 commit comments

Comments
 (0)