É o nome do ficheiro de configuração do pipeline de fornecimento, normalmente
clouddeploy.yaml. Este campo é obrigatório.
REGION
É o nome da região na qual o pipeline de entrega foi criado, por exemplo, us-central1. Este campo é obrigatório.
PROJECT_ID
É o ID do projeto no qual o pipeline de entrega foi criado. Este campo é obrigatório.
O pipeline de entrega está agora num estado suspenso, o que impede a criação, a promoção, a reversão e a reimplementação de lançamentos, bem como a aprovação da implementação.
Implementações de pipelines de entrega suspensos
Se existirem implementações em curso ou em fila quando suspende um pipeline de fornecimento, essas implementações continuam até à conclusão e não são canceladas. No entanto, como não pode criar nem promover um lançamento, não é possível criar novas implementações com essa conduta até que seja retomada.
Autorizações de IAM necessárias para suspender um pipeline
As autorizações de IAM necessárias para suspender um pipeline de entrega
estão incluídas nas seguintes funções:
roles/clouddeploy.admin
roles/clouddeploy.operator
roles/clouddeploy.developer
Retome um pipeline de fornecimento suspenso
Para reativar um pipeline de entrega suspenso:
No ficheiro de configuração do pipeline de entrega, remova a propriedade
suspended: true ou defina-a como false.
Todos os pipelines de fornecimento bloqueados são apresentados com um ícone de cadeado junto ao nome na vista Google Cloud console Pipelines de fornecimento:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-21 UTC."],[[["\u003cp\u003eSuspending a Cloud Deploy delivery pipeline prevents actions such as creating, promoting, rolling back, or redeploying releases, as well as approving or rejecting rollouts.\u003c/p\u003e\n"],["\u003cp\u003eA delivery pipeline can be suspended by including the \u003ccode\u003esuspended: true\u003c/code\u003e property in the pipeline's configuration file, typically \u003ccode\u003eclouddeploy.yaml\u003c/code\u003e, at the top level.\u003c/p\u003e\n"],["\u003cp\u003eRollouts already in progress will complete even after the pipeline is suspended, but no new rollouts can be created.\u003c/p\u003e\n"],["\u003cp\u003eTo resume a suspended delivery pipeline, remove the \u003ccode\u003esuspended: true\u003c/code\u003e property or set it to \u003ccode\u003efalse\u003c/code\u003e in the configuration file and then apply the configuration.\u003c/p\u003e\n"],["\u003cp\u003eSuspended pipelines are identified by a lock icon in the Google Cloud console's Delivery pipelines view.\u003c/p\u003e\n"]]],[],null,["# Suspend a delivery pipeline\n\nThis page describes how to suspend a Cloud Deploy delivery pipeline.\n\nYou can *suspend* a delivery pipeline. Suspending a pipeline means that it can\nno longer be used for the following:\n\n- Create a release\n\n- Promote a release\n\n- Roll back a release\n\n- Redeploy a release\n\n- Approve or reject a rollout\n\nHere are some possible reasons for suspending a delivery pipeline:\n\n- There's a problem with a release and you want to prevent further action on\n that pipeline until the problem is found.\n\n- Your organization observes a holiday freeze, for example during peak holiday\n shopping season.\n\nTo suspend a delivery pipeline:\n\n1. In the delivery pipeline configuration file, include the following property:\n\n suspended: true\n\n This property goes at the top level, as shown: \n\n apiVersion: deploy.cloud.google.com/v1\n kind: DeliveryPipeline\n metadata:\n Name: my-app\n description: main application pipeline\n suspended: true\n serialPipeline:\n stages:\n - targetId: dev\n profiles: []\n - targetId: staging\n profiles: []\n - targetId: prod\n profiles: []\n\n2. Register the delivery pipeline:\n\n gcloud deploy apply --file=\u003cvar label=\"pipeline\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_CONFIG\u003c/span\u003e\u003c/var\u003e --region=\u003cvar label=\"region\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e --project=\u003cvar label=\"project id\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e\n\n Where:\n - \u003cvar translate=\"no\"\u003ePIPELINE_CONFIG\u003c/var\u003e\n\n Is the name of the delivery pipeline configuration file, typically\n `clouddeploy.yaml`. This is required.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Is the name of the region in which the delivery pipeline was created, for\n example `us-central1`. This is required.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n Is the project ID of the project in which the delivery pipeline was\n created. This is required.\n\nThe delivery pipeline is now in a suspended state, which prevents release\ncreation, promotion, rollback and redeploy, and rollout approval.\n\nRollouts from suspended delivery pipelines\n------------------------------------------\n\nIf there are any rollouts in progress or queued when you suspend a delivery\npipeline, those rollouts continue to completion---they are not\ncanceled. However, because you can't create or promote a release, no new\nrollouts can be created using that pipeline until it's [resumed](#resume_a_suspended_delivery_pipeline).\n\nIAM permissions required for suspending a pipeline\n--------------------------------------------------\n\nThe IAM permissions required for suspending a delivery pipeline\nare included in the following roles:\n\n- roles/clouddeploy.admin\n\n- roles/clouddeploy.operator\n\n- roles/clouddeploy.developer\n\nResume a suspended delivery pipeline\n------------------------------------\n\nTo re-enable a suspended delivery pipeline:\n\n1. In the delivery pipeline configuration file, remove the property\n `suspended: true`, or set it to `false`.\n\n2. Apply the configuration:\n\n gcloud deploy apply --file=\u003cvar label=\"pipeline\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_CONFIG\u003c/span\u003e\u003c/var\u003e --region=\u003cvar label=\"region\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e --project=\u003cvar label=\"project id\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e\n\nFind out what pipelines are suspended\n-------------------------------------\n\nAny delivery pipelines that are locked are shown with a lock icon next to the\nname in the Google Cloud console **Delivery pipelines** view:\n\nWhat's next\n-----------\n\n- Find out how to [view a delivery pipeline](/deploy/docs/view-pipeline)\n that's already in use.\n\n- Learn how to [update a delivery pipeline](/deploy/docs/update-pipeline).\n\n- Find out how to [delete a delivery pipeline](/deploy/docs/delete-pipeline).\n\n- Learn how to [use service notifications](/deploy/docs/subscribe-deploy-notifications)"]]