We will need to change the CLI to cope with these changes. Please create a github issue in tooling.
On Thu, Oct 17, 2019 at 10:21 PM Rajith Roshan <[email protected]> wrote: > Hi all, > The current microgateway version(3.0.2) requires at least two open API > vendor extensions to generate the microgateway executable artifact. Those > extensions are > 1. x-wso2-basePath -- specify the base path which is the sub context > which categorize all the http operation defined in the open API > 2. x-wso2-production-endpoints -- specify the actual implementation url of > the endpoint. > > With the next version onward, we are planning to support the open APIs > predefined attributes. > Based on the open API version these attributes may differ. > > Open API version 2 : The actual service endpoint is defined using a > combination of three attributes[1]. 1. Scheme(http,https) 2. host 3. > basePath > Open API version 3 - The backend complete url is defined as array of urls > under the attribute servers[2]. > > So based on the open API version, if the developer provided open API > contains either combination of scheme, host and base path(open API 2) or > the server urls(open API 3), micro gateway will not look for the wso2 > specific vendor extensions. > Any how users can use the extensions to achieve tasks like providing > failover endpoints, throttling, interceptors and etc. > > [1] - https://swagger.io/docs/specification/2-0/api-host-and-base-path/ > [2] - https://swagger.io/docs/specification/api-host-and-base-path/ > > Thanks! > Rajith > > -- > *Rajith Roshan* | Associate Technical Lead | WSO2 Inc. > (m) +94-717-064-214 | (e) [email protected] <[email protected]> > > <https://wso2.com/signature> > -- *Harsha Kumara* Technical Lead, WSO2 Inc. Mobile: +94775505618 Email: [email protected] Blog: harshcreationz.blogspot.com GET INTEGRATION AGILE Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
