Limit on revisions per API proxy

tyoung
Participant I

I just received an email from Apigee with the subject "[Action Required] Review Apigee Edge Product Limits", and a link to this page https://docs.apigee.com/api-platform/reference/limits I understand all of the limits and how to comply with them, except this one:

Number of revisions per API proxy 50

I make changes to a couple of our proxies pretty frequently, so one of them has over 110 revisions. What should I do to stay within the published limit?

I really don't need anything more than the 2-3 most recent revisions (I put my Apigee proxies in TFS for version control and history), but I don't know of any way to delete old revisions.

Is the expectation that we would periodically create new proxies and delete the old ones to eliminate old revisions?

3 8 1,488
8 REPLIES 8

thanks for your question. It's a good one.

Customers I am familiar with, follow this general pattern:

  1. store proxy configuration in source code control. (git repo, TFS, etc). Do not use Apigee Edge as the source-code control system.
  2. deploy new proxies by checking out from the repo, and CI/CD automated import + deploy
  3. The import from above will create a new "revision". Periodically (once a week?) use a culling script that deletes old revisions.

The curl for step 3 looks like:

curl -i -X DELETE -u myuser@example.com \
  https://api.enterprise.apigee.com/v1/o/$ORG/apis/PROXY/revisions/N

There is a nodejs-based tool that helps with this, too. cleanOldRevisions. It lets you keep the most recent N revisions. I often keep 5. I know others who like to retain more. 50 seems really ... unnecessary, to me. I've never seen anyone that really needs that.

You will want to take care not to try to delete a revision that is deployed. The script I mentioned above checks for that.

Okay, so there's no UI to cull old revisions, but you can do it with a simple curl. Nice, thanks, that should work fine.

I've never figured out how to authenticate to use the Apigee APIs, though, so that will be my next project. 🙂

oh yah,

probably oauth.

Here's the doc:

https://docs.apigee.com/api-platform/system-administration/management-api-tokens

BTW, the script I mentioned above ^^ does the oauth authentication automatically.

Hello @Dino-at-Google
i know the post is too old, i was checking the link provided for cleanOldRevisions tool and its returning 404 not found.
can we have an updated link if it is still available please ?
https://github.com/DinoChiesa/apigee-edge-js/blob/master/examples/cleanOldRevisions.js

Sorry about the broken link! I shifted repos. This is the updated one:

https://github.com/DinoChiesa/apigee-edge-js-examples/blob/master/cleanOldRevisions.js

Understanding that this is an old question, is there a way or a plan to be able to configure this quota/limit by the team running the apigee on prem installation in my company? It seems reasonable that this would be a field in a db and not a hard coded limit.

Your view seems a reasonable one.

Maybe @Bala Kasiviswanathan can comment.

Not applicable

What I came to know is the limit is not applicable for Apigee onprem version. I had created a script to clean the old revisions of proxy. for more you can see

https://github.com/priyadarshiajitav1990/APIGEE_MIGRATION_PAJ/tree/clean_revisions