Batalkan deployment revisi proxy API dari cluster Anda seperti yang dijelaskan di bagian berikut.
Perhatikan bahwa saat Anda membatalkan deployment revisi:
Apigee tidak melakukan roll back revisi ke revisi yang sebelumnya di-deploy.
Setelah di-un-deploy, tidak ada revisi proxy API yang di-deploy di lingkungan.
Membatalkan deployment proxy API mirip dengan menghapus proxy API, kecuali
bahwa saat membatalkan deployment revisi, Anda dapat memilih untuk mengeditnya di UI dan men-deploy-nya kembali nanti. Jika Anda
menghapus proxy API, proxy tersebut tidak lagi tersedia untuk diedit.
Apigee di Konsol Cloud
Untuk membatalkan deployment proxy API menggunakan UI:
Di konsol Google Cloud , buka halaman Proxy Development > API Proxies.
UI menampilkan daftar proxy API saat ini untuk lingkungan yang dipilih:
Pilih proxy API yang ingin Anda batalkan deployment-nya.
UI menampilkan tampilan Overview proxy API.
Di baris lingkungan yang diinginkan, luaskan menu drop-down Revisi, lalu
pilih Batalkan deployment:
UI akan meminta Anda untuk mengonfirmasi versi yang ingin dibatalkan deployment-nya:
Klik Batalkan deployment.
UI memperbarui status untuk menunjukkan bahwa revisi telah di-un-deploy dari cluster
segera:
Namun, perhatikan bahwa proses pembatalan deployment dapat memerlukan waktu beberapa saat (dalam model konsistensi
pada akhirnya). Faktanya, saat Anda mengklik Undeploy, Apigee memulai
proses membatalkan deployment revisi yang dipilih dari lingkungan tersebut di cluster.
Untuk mengetahui informasi tentang cara memeriksa status proxy yang tidak di-deploy, lihat
Melihat status deployment.
Atau, Anda dapat membatalkan deployment revisi saat ini yang sedang Anda edit di tab
Develop:
Klik menu drop-down Deploy to: env_name:
UI menampilkan daftar lingkungan. Di kolom Revisi, UI mencantumkan
revisi yang saat ini di-deploy (atau &emdash; jika tidak ada), dan meminta Anda dengan tombol Deploy
revision dan Undeploy.
Klik tombol Undeploy untuk lingkungan yang diinginkan.
UI akan meminta Anda untuk mengonfirmasi versi yang ingin dibatalkan deployment-nya:
Klik tombol Batalkan deployment.
UI memperbarui status untuk menunjukkan bahwa revisi segera di-un-deploy. Namun,
proses penghapusan deployment dapat memerlukan waktu beberapa saat (dalam model konsisten pada akhirnya). Saat Anda
mengklik Batalkan deployment, Apigee akan memulai proses pembatalan deployment revisi
yang dipilih dari lingkungan tersebut.
Apigee API
Untuk membatalkan deployment proxy API, gunakan panggilan API berikut:
Bagian berikut memberikan contoh penggunaan perintah CLI gcloud alpha apigee untuk
membatalkan deployment revisi proxy API dan memvalidasi pembatalan deployment.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eThis page explains how to undeploy API proxy revisions in Apigee and Apigee hybrid environments, which is similar to deleting an API proxy but allows for future editing and redeployment.\u003c/p\u003e\n"],["\u003cp\u003eUndeploying a revision means no revisions of the API proxy will be deployed in the environment, and Apigee does not roll the revision back to a previous version.\u003c/p\u003e\n"],["\u003cp\u003eThe undeployment process can be initiated through the Apigee UI's new or classic Proxy Editor, as well as via the Apigee API using a \u003ccode\u003ecurl\u003c/code\u003e command or the \u003ccode\u003egcloud\u003c/code\u003e CLI.\u003c/p\u003e\n"],["\u003cp\u003eAfter initiating the undeploy process, Apigee begins the process of removing the revision from the environment, but it may take some time to complete due to the eventually consistent model.\u003c/p\u003e\n"],["\u003cp\u003eYou can validate the success of the undeployment by checking the deployment status in the Apigee UI or by using the \u003ccode\u003egcloud\u003c/code\u003e CLI to list deployments and confirm that no revisions are present.\u003c/p\u003e\n"]]],[],null,["# Undeploying an API proxy\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n| **Note:** To undeploy API proxies in environments enabled for [archive deployments](/apigee/docs/api-platform/fundamentals/environments-overview#deployment-types), see [Deploying and managing\n| archives in an Apigee environment](/apigee/docs/api-platform/deploy/manage-archive-deployments).\n\nUndeploy an API proxy revision from your cluster as described in the following sections.\n\nNote that when you undeploy a revision:\n\n- Apigee does not roll the revision back to the previously deployed revision.\n- After undeploying, no revisions of the API proxy are deployed in the environment.\n\nUndeploying an API proxy is similar to [deleting an API proxy](/apigee/docs/api-platform/develop/ui-delete-proxy), except\nthat when you undeploy a revision you can choose to edit it in the UI and later re-deploy it. If you\n*delete* the API proxy, it is no longer available to edit. \n\n### Apigee in Cloud console\n\nTo undeploy an API proxy using the UI:\n\n1. In the Google Cloud console, go to the **Proxy Development \\\u003e API Proxies** page.\n\n [Go to API Proxies](https://console.cloud.google.com/apigee/proxies)\n2. Select the API proxy that you want to undeploy.\n The UI displays the API proxy's **Overview** view.\n\n3. In the **Deployments** section, click **Undeploy**.\n\n4. In the **Undeploy** dialog, click **Confirm**.\n\n### Classic UI\n\nTo undeploy an API proxy using the UI:\n\n1. Sign in to the [Apigee UI](https://apigee.google.com).\n2. Select **Develop \\\u003e API Proxies** .\n\n The UI displays a list of current API proxies for the selected environment:\n\n3. Select the API proxy that you want to undeploy.\n\n The UI displays the API proxy's **Overview** view.\n4. In the desired environment row, expand the **Revision** drop-down list and select **Undeploy** :\n\n The UI prompts you to confirm the version you want to undeploy:\n\n5. Click **Undeploy** .\n\n The UI updates the status to show that the revision was undeployed from the cluster\n immediately:\n\n Note, though, that the undeployment process can take some time (in the *eventually\n consistent* model). In fact, when you click **Undeploy** , Apigee *begins*\n the process of undeploying the selected revision from that environment in the cluster.\n\n For information on how to check the status of the undeployed proxy, see\n [Viewing deployment status](/apigee/docs/api-platform/deploy/ui-deploy-overview#viewing-deployment-status).\n\nAlternatively, you can undeploy the current revision that you are editing in the\n**Develop** tab:\n\n1. Click the **Deploy to: *env_name*** drop-down list:\n\n The UI displays a list of environments. In the **Revision** column, the UI lists\n the currently deployed revision (or **---** if none), and prompts you with **Deploy\n \u003cvar translate=\"no\"\u003erevision\u003c/var\u003e** and **Undeploy** buttons.\n2. Click the **Undeploy** button for the desired environment.\n\n The UI prompts you to confirm the version you want to undeploy:\n\n3. Click the **Undeploy** button.\n\n The UI updates the status to show that the revision was undeployed immediately. However,\n the undeployment process can take some time (in the *eventually consistent* model). When you\n click **Undeploy**, Apigee begins the process of undeploying the selected\n revision from that environment.\n\n### Apigee API\n\nTo undeploy an API proxy, use the following API call: \n\n```\ncurl \"https://apigee.googleapis.com/v1/organizations/$ORG/environments/$ENV/apis/$API/revisions/$REV/deployments\" \\\n -X DELETE \\\n -H \"Authorization: Bearer $TOKEN\"\n```\n\nWhere `$TOKEN` is set to your OAuth 2.0 access token, as described in\n[Obtaining an OAuth 2.0 access token](/apigee/docs/api-platform/get-started/api-get-started#oauth20). For information about the `curl` options used in this example, see\n[Using curl](/apigee/docs/api-platform/get-started/api-get-started#curl). For a description of environment variables you can use, see\n[Setting\nenvironment variables for Apigee API requests](/apigee/docs/api-platform/get-started/api-get-started#api-environment-variables).\n\nThe following provides an example of the response output (an empty response): \n\n```\n{}\n```\n\nFor more information, see the [Undeploy API proxy revision API](/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.apis.revisions.deployments/undeploy).\n\n### gcloud\n\n\nThe following sections provide examples of using `gcloud alpha apigee` CLI commands to\nundeploy API proxy revisions and validate the undeployment.\n\n- [Undeploying an API proxy revision using the gcloud CLI](#undeploy-api-revision-cli)\n- [Validating the undeployment of an API proxy revision using the gcloud CLI](#validate-undeployment-cli)\n\n\nFor more information and a description of the environment variables used in the examples,\nsee [Getting started using gcloud with Apigee](/apigee/docs/api-platform/get-started/gcloud-get-started).\n\n#### Undeploying an API proxy revision using the gcloud CLI\n\n\nTo undeploy an API proxy revision, use the following gcloud command: \n\n```\ngcloud alpha apigee apis undeploy $REV --api=$API --environment=$ENV\n```\n\n\nThe following provides an example of the response: \n\n```\nUsing Apigee organization `my-org`\n```\n\n#### Validating the undeployment of an API proxy revision using the gcloud CLI\n\n\nTo validate that the API proxy revision has been undeployed from the environment, use the following gcloud command: \n\n```\ngcloud alpha apigee deployments list --api=$API --environment=$ENV\n```\n\n\nThe following provides an example of the response: \n\n```\nUsing Apigee organization `my-org`\nListed 0 items.\n```\n\n\nFor more information, see [List deployments CLI](/sdk/gcloud/reference/alpha/apigee/deployments/list)."]]