Cloud Build service account

Related topics

• Artifact Registry Writer configures Cloud Build service account From the official documentation: “If you also use Cloud Build to upload artifacts to repositories, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Writer role to the Cloud Build service account.”
• Cloud Build service account depends on Cloud Deploy From the official documentation: “Grant the Cloud Build service account the permissions needed to invoke Cloud Deploy operations:”
• Cloud Build service account depends on Cloud SQL instance From the official documentation: “Make sure your [Cloud Build service account](/build/docs/cloud-build-service-account) has the [IAM roles and permissions required to connect to the Cloud SQL instance](/sql/docs/mysql/project-access-control#roles).”
• Cloud Build service account depends on Secret Manager From the official documentation: “In order for the Cloud Build service account to access this secret, you will have to grant it the [Secret Manager Secret Accessor](/iam/docs/roles-permissions/secretmanager) role in [IAM](https://console.cloud.google.com/iam-admin/iam).”
• Cloud Run functions depends on Cloud Build service account From the official documentation: “Cloud Run functions uses the [Cloud Build service account](/build/docs/cloud-build-service-account) in the same Google Cloud project to build and deploy your function.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• Application Default Credentials secures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Run functions works with Cloud Storage From the official documentation: “(GCF translates GCS notifications to HTTP requests internally)”
• Cloud Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Build works with Cloud Deploy From the official documentation: “The pipeline uses Cloud Build for CI and Cloud Deploy for CD.”
• Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Deploy works with Cloud Storage From the official documentation: “Delete the Cloud Storage buckets that Cloud Deploy created.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Cloud Build depends on Secret Manager From the official documentation: “Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only.”
• Cloud Deploy depends on Pub/Sub From the official documentation: “Cloud Deploy uses Pub/Sub to publish notifications for two purposes:”
• Cloud Deploy works with Pub/Sub From the official documentation: “Cloud Deploy publishes operational messages to Pub/Sub.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud Run functions works with Secret Manager From the official documentation: “[Secret Manager](/secret-manager) stores the Cloud Run functions secrets.”
• Cloud Run functions depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
• Application Default Credentials works with Cloud Build From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials secures Cloud SQL instance From the official documentation: “This library uses [Application Default Credentials](https://developers.google.com/identity/protocols/application-default-credentials) to authenticate the connection to the Cloud SQL server.”
• Application Default Credentials secures Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Cloud Build depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
• Cloud Build works with Cloud Run functions From the official documentation: “The act of deploying a Cloud Run function automatically coordinates underlying Google Cloud services, including Cloud Storage, Cloud Build, and Artifact Registry, to package and run your code.”
• Cloud Build works with Cloud SQL instance From the official documentation: “To connect to your Cloud SQL instance over private IP, Cloud Build must be in the same VPC network as your Cloud SQL instance.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build works with Pub/Sub From the official documentation: “Cloud Build sends all build event updates, along with build metadata, [to Pub/Sub](/build/docs/subscribe-build-notifications) on either the `cloud-builds` topic or a user-defined topic.”
• Cloud Build depends on service account From the official documentation: “Cloud Build uses a service account to execute builds on your behalf.”
• Cloud Deploy depends on Cloud Build From the official documentation: “Cloud Deploy calls Cloud Build to render your manifests and to deploy to the target runtime.”
• Cloud Run is an alternative to Cloud Run functions From the official documentation: “The blueprint supports the following use cases: - Deploying a serverless architecture using Cloud Run functions (this document) - [Deploying a serverless architecture using Cloud Run](/architecture/blueprints/serverless-blueprint)”