I watched the video on creating a Console To-Go.
I saw how, with WADL, you can assist developer usage and auto-generate documentation for your own web site.
I did not see how you manage different versions of backend APIs.
What do you do when there is a new version of the API? Do you just create a whole new proxy?
Solved! Go to Solution.
If you want to make more than one versions of your APIs co-exist in Apigee layer you need to add another proxy.xml in the present application-bundle, with a new context path (basepath in apigee terms) however. E.g.,
/v1/customers
/v2/customers
When there are multiple backend versions you can do the following
If you want to make more than one versions of your APIs co-exist in Apigee layer you need to add another proxy.xml in the present application-bundle, with a new context path (basepath in apigee terms) however. E.g.,
/v1/customers
/v2/customers
When there are multiple backend versions you can do the following
Hi, doesn't this conflict with the Antipattern: Define multiple ProxyEndpoints in an API proxy?
https://docs.apigee.com/api-platform/antipatterns/multiple-proxyendpoints
This is to support for a particular time frame. You can also create separate proxy as well. If you have separate basepath same proxy with multiple revisions can be deployed.
2 years ago i gave a presentation about one of the ways we have done versioning
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |