Hi All, I'm implementing a dynamic backend endpoint feature which will provide users the capability to define dedicated backends for the same API.
This feature is a bit similar to what we have in API Manager where we define endpoints with variables and resolve it during the runtime (say we set backend endpoint as http://{uri.var.host}:{uri.var.port}/apis/weather and resolve them using system variables, etc). Similarly, We plan to provide a method to override the backend endpoint uri from the API. But this method doesn't depend on whether the URL is defined with template structure (with {uri.var.host}, etc). For example, If there is an API with TestAPI and version 1.0, we could define *TestAPI-1.0.prod.**ep* , *TestAPI-1.0.sand.ep* as environment variables, value in the TOML format or as command-line parameters and override the existing related endpoint during the startup time. If the properties are not provided, then we use endpoint defined in the API as the default endpoint. This way, a user can start the micro-gateway with the default backend endpoint or he can override it during the startup time. This will give the capability to call dedicated endpoints for each environment Chamila. -- Regards, Chamila Adhikarinayake WSO2, Inc. Mobile - +94712346437 Email - [email protected] Blog - http://helpfromadhi.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
