Solved: api proxy's revision implementation - Page 2

bhatikuldeep · 02-04-2015 08:43 AM

its kind of an architectural question, i see revisions are associated to an api proxy and not to an environment with in api proxy, there must be a reason for this setup with in apigee which i am not sure about, what a best possible way to implement is to have revision with in each environment, let me know if this is right way to have it in apigee as new feature/enhancement ?

Report Inappropriate Content

You can always save a proxy as a new revision. Then, you have the option of deploying that revision to either environment. When you click on the Revision button, it will show all of the revisions for the proxy as well as which revision is deployed to which environment.

View solution in original post

divyaachan

An org can have different environments and the apiproxy can be deployed to any environment. The revisions of an apiproxy is basically comparable to a version of an application that can be deployed to many environments.

So, for e.g. an org 'abc' can have , say 2 environments, prod and test. 'abc' org has 2 apiproxies 'test' and 'sample'.

apiproxy 'test' can have as many revisions so rev1 can be deployed to prod and rev2 can be deployed to test env. or the same revision 1 can be deployed to both prod and test environment.

Apiproxy here can be thought of as an application that has different versions deployed to different environments.

View solution in original post