on 09-10-2020 9:14 AM
Hi everyone,
I'm setting up a series of API proxies that will share a config file. To help manage change, I'm considering turning this config file into it's own microservice, negating the need to store and maintain config data in each proxy.
I noticed on the below article from Apigee Edge that there is a concept around environment level resource files. As I understand it, I could setup a Javascript file that any of the proxies could directly reference. However, the examples for listing/managing these resources are geared for Apigee Edge's own hosted solution. Does anyone know if SAP APIM has the same functionality?
Hi Logan,
Unfortunately I do not believe that we give customers access to environment level resource storage. What you could do however is is create a Policy Template with the JS, which will apply the JS to any Proxy you wish.
Regards,
Elijah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elijah,
Many thanks for getting back to me. I did consider using the policy template as a potential solution. But if my understanding is correct, once you apply a template to a proxy, it's a one time thing. As in, if I make changes to the template, it wont automatically cascade those changes to say the other 50 proxies that all used it. So I would still have to edit each proxy to ensure the updates/change are applied. I have however, created a proxy that can accept a query parameter. This in turn is handled by a Javascript file to do the work of returning the configuration that has been requested back to the caller. Seems to work ok, although early days.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.