This pageapplies toApigee andApigee hybrid.

View Apigee Edge documentation.

When you make a change to an API proxy, you can save it as a new revision and deploy it to yourcluster.

• Deploying an API proxy
• Undeploying an API proxy

About deployment

The deployment lifecycle of an API proxy revision on Apigee is shown in the following figure.

• If you make any changes to an API proxy, you must deploy it as a new revision.
• After you deploy an API proxy, the revision is read-only. You cannot change an API proxy revision (such as to make incremental changes); the only way tochange a revision is to create a new revision and deploy it.
• MPs can deploy a proxy bundle only in its entirety. If you make changes to individual fragments or policies, the MPs will still deploy the entire proxy bundle.
• If your Apigee usage distinguishes betweenStandard and Extensible proxies, when deploying a revision that changes an API proxy from a Standard proxy to an Extensible proxy:
  • a cost might be incurred. If you are a Pay-as-you-go customer, see thePay-as-you-go entitlements. If you are a Subscription customer, see your plan's details.
  • the deployment requires additional time. During the deployment window the API call flow is not disrupted but you can't deploy, undeploy, or delete the proxy. Also, current or new revisions cannot be deleted during the deployment window. Changes to the API proxy and new revision creation are allowed.

Zero-downtime deployment

All successful API proxy deployments to Apigee, arezero-downtime deployments. API proxy deployments happen in this order:

1. Revision 1 of the API proxy/hello is deployed and handling traffic.
2. Revision 2 of/hello is deployed.
3. Revision 2 is deployed to the Message Processors in the runtime plane.
4. Revision 1 is undeployed.

The API proxy revision deployment is now complete with no downtime.

Deploying an API proxy on Apigee does not make it immediately available. It takes time forthe API proxy to be synchronized across allMPs in the runtime plane. However, Apigee providestools that can give you some information about the status of your API proxy revisions.

curl "https://apigee.googleapis.com/v1/organizations/$ORG/environments/$ENV/apis/$API/revisions/$REV/deployments" \  -X GET \  -H "Authorization: Bearer $TOKEN"

{  "environment": "test",  "apiProxy": "helloworld",  "revision": "1",  "deployStartTime": "1559149080457",  "pods": [    {      "podName": "apigee-runtime-myorg-test-f8bdf9d-2s72w",      "deploymentStatus": "deployed",      "statusCodeDetails": "Deployment Success",      "podStatus": "active",      "podStatusTime": "1595357668001"    }  ],  "state": "READY"}

gcloud alpha apigee deployments describe --api=$API --environment=$ENV

Using Apigee organization `my-org`Using deployed revision `1`apiProxy: helloworlddeployStartTime: '1598032332802'environment: testpods:- deploymentStatus: deployed  podName: apigee-runtime-myorg-test-f8bdf9d-2s72w  podStatus: active  podStatusTime: '1598302128087'  statusCodeDetails: Deployment Successrevision: '1'state: READY

View proxy deployment usage

The usage of API proxies in your organization may be subject to a deployments quota, which is a limit on how many deployment units you can use at a time. See your entitlements (Pay-as-you-go orSubscription) for details. You can view your organization's proxy deployment usage from several places within theApigee UI in Cloud console, as described below.

1. In the Google Cloud console, go to theOverview page.

   Go to Overview

2. You can view proxy deployment usage for your organization at a glance using theProxy Usage card, whichdisplays the following information for your organization:
   • Total proxies created: The total number of API proxies created, including deployed and undeployed proxies.
   • Proxies deployed: The total number of API proxies deployed across all environment(s) in the organization.
   • Proxy deployment units: The total number of API proxy or shared flow revisions deployed in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Proxies and shared flows deployed against limit: Total number of API proxies and shared flows deployed in the organization, against the limit for your organization type.
   • Extensible deployment units: The number of extensible API proxy revisions deployed in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Standard deployment units: The number of standard API proxy revisions deployed in your organization. Each deployment per environment, per instance, is counted as one unit.

View deployment usage on the API Proxies page

To view your API proxy deployment usage from theAPI Proxies page:

1. In the Google Cloud console, go to theAPI Proxies page.

   Go to API Proxies

2. TheAPI Proxies page displays the following information:
   • Total proxies created: The total number of API proxies developed in your organization, including deployed and undeployed proxies.
   • Proxies deployed: The total number of API proxy revisions deployed across all environments in your organization.
   • Proxy deployment units: The total number of API proxy or shared flow revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Extensible proxy deployment units: The number of extensible API proxy revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Standard proxy deployment units: The number of standard API proxy revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.

View deployment usage on the Environments page

To view your API proxy deployment usage from theEnvironments page:

1. In the Google Cloud console, go to theEnvironments page.

   Go to Environments

2. Select theEnvironments overview tab to display the following information for all of the environments:
   • Total proxy deployment units: The total number of API proxy or shared flow revisions deployed across all environments in your organization.
   • Extensible proxy deployment units: The number of extensible API proxy revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Standard proxy deployment units: The number of standard API proxy revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.
   • Shared flow deployment units: The total number of shared flow revisions deployed across all environments in your organization. Each deployment per environment, per instance, is counted as one unit.
3. To view proxy deployment usage for a single environment:
   1. In theEnvironments list, select an environment name to view its details.
   2. Select theDeployments tab to view deployment unit usage for the selected environment.

Next steps