Solved: Specify revision when creating an API proxy

johni_tcna · 08-11-2023 10:32 AM

Is there any way to specify a revision when creating an API proxy? This is my scenario:

We have two organizations, nonprod and prod. Development is done in the nonprod org in the dev environment. Prod has two environments - stg and prd. What we want to do is to have the revisions in stg and prd match what's in dev.

Example workflow:

API proxy is created and developed in nonprod dev.
API proxy is iterated every time it is updated, i.e. revision 8
API proxy is promoted to stg environment.

Ideally, the revision promoted to stg is also revision 8, but since it is pushing to a new org, it will be revision 1. Is there a way to preserve that across organizations? Thanks!

dchiesa1

No, there is no way to do that. You always will get monotonically increasing revision numbers, distinct for each organization.
Some customers will compute a SHA256 sum of the proxy configuration, and insert that into the Description of the proxy. That sum might be a way for you to determine whether revision N in organization 1 is the same as revision M in organization 2. Other customers use the proxyname itself to track that information. They might append a version number to the proxy name. This would be YOUR definition of version, distinct from the "Revision" tracked by Apigee.

View solution in original post

dchiesa1

No, there is no way to do that. You always will get monotonically increasing revision numbers, distinct for each organization.
Some customers will compute a SHA256 sum of the proxy configuration, and insert that into the Description of the proxy. That sum might be a way for you to determine whether revision N in organization 1 is the same as revision M in organization 2. Other customers use the proxyname itself to track that information. They might append a version number to the proxy name. This would be YOUR definition of version, distinct from the "Revision" tracked by Apigee.