rollout

Related topics

• advance a rollout configures rollout From the official documentation: “Advances a rollout.”
• phase is part of rollout From the official documentation: “A phase is a sub-message in a rollout.”
• Cancel a rollout configures rollout From the official documentation: “Cancel a Rollout.”
• Job is part of rollout From the official documentation: “Job The specific operation to be performed on a rollout, such as deploy or verify.”
• job run is part of rollout From the official documentation: “Job run A child of the rollout resource, the job run is an instance of a job, for example an attempt to deploy.”
• rollout is part of Cloud Deploy From the official documentation: “Create and manage Rollout resources for Cloud Deploy.”
• rollout is part of delivery pipeline From the official documentation: “If you have a delivery pipeline without any subresources (releases or rollouts), you can delete it by running the following command:”
• rollout is part of release From the official documentation: “You can view a list of rollouts for this release, and click a rollout to [view rollout details](#viewing_rollouts).”
• rollout depends on release From the official documentation: “When you roll back a target, Cloud Deploy creates a new `rollout` resource based on a previous release.”
• rollout is part of Service Management API From the official documentation: “A `Rollout` defines how Google Service Management should deploy service configurations to backend systems and how the configurations take effect at runtime.”
• Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• 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:”
• analysis job is part of Cloud Deploy From the official documentation: “By default, Cloud Deploy analysis can use many types of metrics from Google Cloud Observability.”
• analysis job is part of delivery pipeline From the official documentation: “Your analysis job is configured as part of the delivery pipeline definition, inside a `strategy` stanza.”
• Automation is part of Cloud Deploy From the official documentation: “Deletes a Cloud Deploy Automation.”
• Automation is part of delivery pipeline From the official documentation: “All automations exist only within the scope of one delivery pipeline.”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Service Management API From the official documentation: “Cloud Audit Logs for Service Management let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Deploy depends on Cloud Audit Logs From the official documentation: “The Cloud Deploy service agent is a service account that Cloud Deploy uses to interact with other Google Cloud services that Cloud Deploy relies on. These services include Cloud Build, Pub/Sub, and Cloud Audit Logs.”
• Cloud Deploy depends on Identity and Access Management From the official documentation: “In addition to other Identity and Access Management permissions you need for using Cloud Deploy, you need the following permissions in order to perform additional actions that might be needed for a canary deployment:”
• Cloud Run works with target From the official documentation: “You now have a pipeline, with one multi-target comprising two GKE or Cloud Run targets, ready to deploy your application.”
• delivery pipeline is part of Cloud Deploy From the official documentation: “Delivery Pipeline being managed by Cloud Deploy.”
• delivery pipeline configures release From the official documentation: “The delivery pipeline defines the lifecycle of that release.”
• Identity and Access Management secures Cloud Audit Logs From the official documentation: “IAM permissions and roles determine your ability to access audit logs data in the [Logging API](/logging/docs/reference/v2/rest), the [Logs Explorer](/logging/docs/view/logs-explorer-interface), and the [Google Cloud CLI](/logging/docs/reference/tools/gcloud-logging).”
• Identity and Access Management secures Cloud Deploy From the official documentation: “As with all Google Cloud products, Identity and Access Management protects Cloud Deploy by controlling which authenticated users and service accounts can perform which actions.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management works with Service Management API From the official documentation: “Understand and use Identity and Access Management with the Service Management API.”
• Job is part of Cloud Run From the official documentation: “On Cloud Run, your code can run as a *service*, *job*, *worker pool*, or *instance*.”
• Job is part of phase From the official documentation: “A phase contains one or more jobs (for example deploy, or deploy and verify).”
• job run is part of Job From the official documentation: “And each job can have zero or more job runs. A job run is an instance of a job.”
• release is part of Cloud Deploy From the official documentation: “Create and manage Release resources for Cloud Deploy.”
• release is part of delivery pipeline From the official documentation: “If you have a delivery pipeline without any subresources (releases or rollouts), you can delete it by running the following command:”
• Service Management API depends on Identity and Access Management From the official documentation: “The Service Management API uses [Identity and Access Management](/iam) (Cloud IAM) to control access to managed services and their child resources.”
• target is part of Cloud Deploy From the official documentation: “Create and manage Target resources for Cloud Deploy.”
• target is part of delivery pipeline From the official documentation: “If you change a delivery pipeline, or any of its targets, after a release is created, you can do the following:”