Good question.
In Apigee Edge, the "proxy" is really a combination of
- one or more proxy endpoints, each defined by a base path, some conditional flows, pre- and post-flows, fault rules, route rules, and one or more virtual hosts
- zero or more target endpoints, each with conditional flows, fault rules, and pre- and post-flows.
- resources, of the type JavaScript, Java, WSDL, XSL, nodejs
- policies
When you deploy a proxy, you deploy the whole lot. Everything.
When you deploy a proxy with multiple proxy endpoints, then all of the proxy endpoints are deployed at the same time. This is true whether you use the Edge administrative UI, or the Edge administrative API. In fact the UI layers directly on the API, so ... they both amount to the same thing.
The API call that deploys a proxy is defined here in the documentation. (Thanks! to the Apigee docs team!)
In curl, it looks like this:
curl -u username:password -X POST \
-H content-type:application/x-www-form-urlencoded \
"${mgmtserver}/v1/o/${orgname}/e/${envname}/apis/${apiproxyname}/revisions/${apirevision}/deployments" \
-d "override=true&delay=30"
So really, no difference at all when you deploy an api proxy that has one endpoint, versus multiple endpoints. But this is such a straightforward answer, I'm thinking... maybe that's not what you were asking.
Maybe you are asking - what does an offline API Proxy bundle look like, if it has multiple proxy endpoints?
And for that - you can easily see the structure of the bundle if you just download the revision of the api proxy that you have, which has multiple proxy endpoints. That option is under the Project button in the UI, within the proxy editor page.
You will see something like this:
apiproxy/
apiproxy/your-proxy-name.xml
apiproxy/policies/
apiproxy/policies/AM-CleanResponseHeaders.xml
apiproxy/policies/AM-NoContent.xml
apiproxy/policies/AM-Response.xml
apiproxy/policies/BasicAuth-1.xml
apiproxy/policies/...
apiproxy/proxies/
apiproxy/proxies/resource.xml
apiproxy/proxies/token-dispensary.xml
apiproxy/resources/
apiproxy/resources/jsc/
apiproxy/resources/jsc/dateFormat.js
apiproxy/resources/jsc/groomTokenResponse.js
apiproxy/resources/jsc/...
apiproxy/resources/java/...
apiproxy/resources/node/...
apiproxy/targets/target1.xml
apiproxy/targets/...
Notice - 2 XML files within the proxies subdirectory.
LinkedIn
Twitter
