Apigee Hosted Targets Limit

sdonnelly · 08-21-2019 01:58 AM

We've been hosting our swagger files as part of our proxies which has been highly useful in reminding us to keep our specs up-to-date. However, we have now hit the limit of hosted targets (which we were unaware existed until we trawled through documentation). Has anyone else been hosting swaggers in this manner?

One approach to get around this might be to create a generic proxy that only functions to take a yaml file passed to it and render it, but ideally we'd like to avoid this. So it would be good to hear other community members opinions/experience

dknezic

Hi Simon, could you elaborate on your use case for hosting swagger files within your proxies?

sdonnelly

Hi Dane,

By hosting the swagger in the proxy we have the following benefits:

Swagger code is maintained alongside API and prevents the swagger and API from being at different versions.
Swagger is also rendered using html/css and formatted in the same format as swagger-ui and is given it's own URL.

I'm happy to provide a sample of the proxy code if that'd be useful.

Thanks

dchiesa1

Simon, when you say you are "hosting the swagger in the proxy" , do you mean to say that you are using a hosted target to serve up SwaggerUI from the swagger (openapispec) document that is associated to the proxy?

How does that work?

Explain in just a little more detail.

dchiesa1

yes, the limits on Hosted Targets are sort of unfortunate.

And also a fact of life.

I think it might be better if you used a consolidated hosting arrangement in which a single endpoint could serve up all the "approved" yaml files. Not a "bring your own yaml" but... rather, when you update the proxy, your CI/CD could also post the associated apispec .yaml file to the SwaggrUI app (maybe in AppEngine or whatever) which itself is fronted solely by Apigee-hosted API Proxies.

rmakhim

A fact of life indeed.