Nom du fichier de configuration du pipeline de diffusion, généralement clouddeploy.yaml. Obligatoire.
REGION
Nom de la région dans laquelle le pipeline de diffusion a été créé, par exemple us-central1. Obligatoire.
PROJECT_ID
ID du projet dans lequel le pipeline de diffusion a été créé. Obligatoire.
Le pipeline de livraison est maintenant suspendu, ce qui empêche la création de versions, la promotion, le rollback et le redéploiement, ainsi que l'approbation du déploiement.
Déploiements à partir de pipelines de diffusion suspendus
Si des déploiements sont en cours ou en file d'attente lorsque vous suspendez un pipeline de diffusion, ils se poursuivent jusqu'à leur achèvement. Ils ne sont pas annulés. Toutefois, comme vous ne pouvez pas créer ni promouvoir de version, vous ne pouvez pas créer de nouveaux déploiements à l'aide de ce pipeline tant qu'il n'est pas réactivé.
Autorisations IAM requises pour suspendre un pipeline
Les autorisations IAM requises pour suspendre un pipeline de diffusion sont incluses dans les rôles suivants:
roles/clouddeploy.admin
roles/clouddeploy.operator
roles/clouddeploy.developer
Réactiver un pipeline de diffusion suspendu
Pour réactiver un pipeline de diffusion suspendu:
Dans le fichier de configuration du pipeline de diffusion, supprimez la propriété suspended: true ou définissez-la sur false.
Les pipelines de livraison verrouillés sont associés à une icône en forme de cadenas à côté de leur nom dans la vue Pipelines de livraison de la Google Cloud console:
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/09/03 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/09/03 (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)"]]