Cloud Build triggers

Related topics

• Cloud Build triggers works with Cloud Run From the official documentation: “You can automate the deployment of your software to Cloud Run by creating Cloud Build triggers.”
• Cloud Build triggers is part of Cloud Build From the official documentation: “Open the **Triggers** page of Cloud Build.”
• Cloud Build triggers works with Cloud Scheduler From the official documentation: “You can schedule recurring Image Builder runs by using Cloud Scheduler and Cloud Build triggers.”
• Cloud Build triggers is an alternative to Secret Manager From the official documentation: “You need to use Secret Manager to connect to private GitHub repositories only when running manual builds. When you run builds using Cloud Build triggers, you can automatically connect to any private repository you own without storing your credentials in Secret Manager.”
• 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.”
• Cloud Run works with Cloud Scheduler From the official documentation: “Create a Cloud Scheduler job that triggers the Cloud Run service daily.”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Cloud Scheduler works with Pub/Sub From the official documentation: “Create a Pub/Sub topic to set up as your Cloud Scheduler job target.”
• App Engine is an alternative to Cloud Run From the official documentation: “App Engine and Cloud Run are Google Cloud platforms for hosting apps and services.”
• 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 Scheduler works with Workflows From the official documentation: “[Schedule a workflow using Cloud Scheduler](/workflows/docs/schedule-workflow)”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• App Engine works with Cloud SQL From the official documentation: “You can use Cloud SQL with App Engine applications running in the flexible environment that are written in:”
• Cloud Build works with Cloud SQL From the official documentation: “This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Build.”
• Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• 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 works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
• Cloud Scheduler depends on service account From the official documentation: “To sync a replicated taxonomy across locations with Cloud Scheduler, you need a service account.”
• Pub/Sub works with Workflows From the official documentation: “Pub/Sub can be integrated into multistep serverless [Workflows](/workflows) declaratively.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• App Engine works with Cloud Build From the official documentation: “Cloud Build builds your app and deploys it to App Engine.”
• App Engine works with Pub/Sub From the official documentation: “Pub/Sub is now the preferred way of performing pull queue work in App Engine.”
• Cloud Build works with Cloud Scheduler From the official documentation: “Use Cloud Build triggered by Cloud Scheduler to run a containerized export job on a schedule.”
• 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 Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud SQL works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• Secret Manager works with Workflows From the official documentation: “You can use a Workflows connector to access Secret Manager within a workflow.”
• 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.”
• Workflows depends on service account From the official documentation: “You need a service account for Workflows (to run the pipeline) and for Managed Service for Apache Spark (to run the connector).”
• App Engine depends on Cloud Build From the official documentation: “In addition, all App Engine runtimes now use Cloud Build to build apps into a container during the deployment process.”
• App Engine works with Cloud Scheduler From the official documentation: “Specify the name of the App Engine service that is running the handler for the Cloud Scheduler job.”
• App Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on App Engine, you must grant any [required permissions](/secret-manager/docs/access-control#roles) to the App Engine service.”
• App Engine depends on service account From the official documentation: “App Engine applications require a [service account](/iam/docs/service-accounts) to access other Google Cloud services and execute tasks.”
• 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 Build works with Workflows From the official documentation: “You can run gcloud CLI commands from a Cloud Build step, and you can create that step in Workflows using the Cloud Build connector.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Cloud Scheduler depends on App Engine From the official documentation: “You enable the App Engine API because the Cloud Scheduler service requires App Engine.”
• Cloud Scheduler works with Cloud SQL From the official documentation: “Learn how to use Cloud Scheduler and Cloud Run functions to automatically start and stop Cloud SQL instances on a regular schedule using resource labels.”
• Cloud Scheduler depends on Identity and Access Management From the official documentation: “Cloud Scheduler uses Identity and Access Management (IAM) for authorization.”
• Cloud Scheduler depends on Pub/Sub From the official documentation: “Cloud Pub/Sub (required for Cloud Scheduler to invoke functions)”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Identity and Access Management secures Cloud Build From the official documentation: “To grant other users access, you can grant Identity and Access Management (IAM) roles on the project, or on a specific Cloud Build resource.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”
• Identity and Access Management works with Workflows From the official documentation: “Workflows manages access and authentication using Identity and Access Management (IAM) roles and permissions.”
• Identity and Access Management secures Workflows From the official documentation: “Workflows uses Identity and Access Management (IAM) to control which authenticated users and service accounts can perform which actions.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”
• service account secures Cloud SQL From the official documentation: “Cloud SQL uses service accounts for authentication between Cloud SQL and other Google Cloud products.”