Seamless proxy deployment does not undeploy prior revision

When deploying a proxy revision to an environment using the Edge API, I consistently see that any prior deployed revisions remain.

A simple way I can repro this:

Upload a proxy via API, get revision 1. (i.e. https://api.enterprise.apigee.com/v1/organizations/{org}/apis?action=import&name={proxy-name} )

Deploy proxy (i.e. https://api.enterprise.apigee.com/v1/organizations/{org}/environments/dev/apis/{proxy-name}/revisions/1/deployments?override=true&delay=10 )

Save revision 1 as new revision 2

Deploy revision 2 (i.e. https://api.enterprise.apigee.com/v1/organizations/{org}/environments/dev/apis/{proxy-name}/revisions/2/deployments?override=true&delay=10 )

Repeat for each new proxy version.

I would have expected each prior revision to undeploy after 10 seconds as per the request. Am I not understanding the usage of this API correctly?

For reference, I am using Apigee Edge Public Cloud

That seems wrong!

If I were you I would connect with Apigee support to get their help resolving this problem.

1 Like