Hi all Tested the following scenarios for Microgateway 3.2.0 RC2.
Using K8s-API-Operator: 1. API secured with Basic Authentication 2. API secured with JWT 3. Rate Limiting 4. Ballerina Interceptors No blockers found. *[+] Stable* - Go ahead and release Thanks and regards, Renuka On Tue, Aug 25, 2020 at 2:39 PM Heshan Sudarshana <hesh...@wso2.com> wrote: > Hi all, > > Tested the following scenarios for Microgateway 3.2.0 RC2. > > - HTTP2 support > - Global throttling (API, resource, application, subscription levels) > - Mutual SSL (mandatory/optional) > - API level throttle tiers > - API Resource level throttle tiers > - Custom policy throttling and blocking conditions > - Conditional Throttling > > No blockers found. > > *[+] Stable* - Go ahead and release > > Thanks and regards, > Heshan. > > On Tue, Aug 25, 2020 at 1:19 AM Chashika Weerathunga <chash...@wso2.com> > wrote: > >> Hi all, >> >> Tested the following scenarios for Microgateway 3.2.0 RC2. >> >> >> - Microgateway labeling >> - Microgateway analytics report >> - Analytics file writing >> - Analytics file uploading/publishing >> - Analytics GRPC publishing >> - Endpoint override for imported APIs >> - Endpoint override for Developer-first Approach APIs >> - Load balance and failover endpoints >> - Custom header and header sent to back end >> - Java interceptors >> - Ballerina interceptors >> - Advance endpoint configurations >> >> >> No blockers found. >> >> *[+] Stable* - Go ahead and release >> >> Thanks & Regards >> >> On Mon, Aug 24, 2020 at 2:22 PM Menaka Jayawardena <men...@wso2.com> >> wrote: >> >>> Hi Amila, >>> >>> I think what you have explained should be the migration guide for 3.2.0. >>>> I think we need to get it added to the docs. Even if there are zero steps >>>> to be followed, that itself should be mentioned in the docs under migration >>>> because otherwise the users will be in doubt. >>> >>> >>> Noted. We will update the docs. >>> >>> Thanks and Regards, >>> Menaka >>> >>> On Mon, Aug 24, 2020 at 2:08 PM Nadee Poornima <nad...@wso2.com> wrote: >>> >>>> Hi Menaka, >>>> Thanks for the detailed explanation. >>>> >>>> I think what you have explained should be the migration guide for >>>>> 3.2.0. I think we need to get it added to the docs. Even if there are zero >>>>> steps to be followed, that itself should be mentioned in the docs under >>>>> migration because otherwise the users will be in doubt. >>>> >>>> >>>> +1 for this. >>>> >>>> Cheers, >>>> Nadee >>>> >>>> On Mon, Aug 24, 2020 at 2:00 PM Amila Maha Arachchi <ami...@wso2.com> >>>> wrote: >>>> >>>>> Hi Menaka, >>>>> >>>>> I think what you have explained should be the migration guide for >>>>> 3.2.0. I think we need to get it added to the docs. Even if there are zero >>>>> steps to be followed, that itself should be mentioned in the docs under >>>>> migration because otherwise the users will be in doubt. >>>>> >>>>> Regards, >>>>> Amila. >>>>> >>>>> On Mon, Aug 24, 2020 at 12:54 PM Menaka Jayawardena <men...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Nadee, >>>>>> >>>>>> By default, Microgateway does not require any migration process. You >>>>>> can build the mgw project using the Microgateway 3.2.0 toolkit and run >>>>>> with >>>>>> the Microgateway 3.2.0 runtime with the old configurations. (Ex. build >>>>>> 3.1.0 project with 3.2.0 toolkit and run with 3.2.0 runtime with the >>>>>> 3.1.0 >>>>>> configs) >>>>>> All most all of the configurations are backwards compatible and there >>>>>> are only few config level changes which will be updated in the docs. >>>>>> (related to authentication and subscription validation). >>>>>> >>>>>> Migration would only be required if you have any customizations >>>>>> written in ballerina. >>>>>> >>>>>> Thanks and Regards, >>>>>> Menaka >>>>>> >>>>>> On Mon, Aug 24, 2020 at 11:37 AM Nadee Poornima <nad...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Menaka, >>>>>>> >>>>>>> Analysed the Micro GW documents[1], however, didn't see any document >>>>>>> relating the migration process (upgrade process) from Micro GW 3.1.0 to >>>>>>> Micro GW 3.2.0. >>>>>>> Is there any specific process to migrate Micro GW product? How we >>>>>>> can do that? >>>>>>> >>>>>>> Appreciate your valuable thought here. >>>>>>> >>>>>>> [1]. https://mg.docs.wso2.com/en/latest/# >>>>>>> >>>>>>> Cheers, >>>>>>> Nadee >>>>>>> >>>>>>> On Sat, Aug 22, 2020 at 4:10 PM Menaka Jayawardena <men...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> WSO2 Api Manager team is pleased to announce the second release >>>>>>>> candidate of WSO2 API Microgateway 3.2.0. >>>>>>>> >>>>>>>> The WSO2 API Microgateway is a lightweight, gateway distribution >>>>>>>> which can be used to expose single or multiple APIs. >>>>>>>> >>>>>>>> Please find the improvements and fixes related to this release in Fixed >>>>>>>> issues >>>>>>>> <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+> >>>>>>>> >>>>>>>> Download the product from here >>>>>>>> <https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc2> >>>>>>>> >>>>>>>> The Tag to be voted upon is >>>>>>>> https://github.com/wso2/product-microgateway/tree/v3.2.0-rc2 >>>>>>>> >>>>>>>> *Documentation*: https://mg.docs.wso2.com/en/latest/ >>>>>>>> >>>>>>>> Please download, test the product and vote. >>>>>>>> >>>>>>>> *[+] Stable* - Go ahead and release >>>>>>>> >>>>>>>> *[-] Broken* - Do not release (explain why) >>>>>>>> >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> WSO2 API Manager Team >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Menaka Jayawardena* >>>>>>>> Senior Software Engineer *|* *WSO2* *Inc*. >>>>>>>> +94 71 350 5470 | men...@wso2.com >>>>>>>> >>>>>>>> <https://wso2.com/signature> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Nadee Poornima* >>>>>>> Software Engineer | WSO2 >>>>>>> >>>>>>> Email : nad...@wso2.com >>>>>>> Mobile : +94713441341 >>>>>>> MyBlog: https://medium.com/nadees-tech-stories >>>>>>> >>>>>>> <https://wso2.com/signature> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Menaka Jayawardena* >>>>>> Senior Software Engineer *|* *WSO2* *Inc*. >>>>>> +94 71 350 5470 | men...@wso2.com >>>>>> >>>>>> <https://wso2.com/signature> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Mahaarachchi* >>>>> VP of Engineering, Integration >>>>> WSO2, Inc.; http://wso2.com >>>>> Mobile: +94719371446 >>>>> >>>>> <http://wso2.com/signature> >>>>> >>>>> >>>> >>>> -- >>>> *Nadee Poornima* >>>> Software Engineer | WSO2 >>>> >>>> Email : nad...@wso2.com >>>> Mobile : +94713441341 >>>> MyBlog: https://medium.com/nadees-tech-stories >>>> >>>> <https://wso2.com/signature> >>>> >>> >>> >>> -- >>> *Menaka Jayawardena* >>> Senior Software Engineer *|* *WSO2* *Inc*. >>> +94 71 350 5470 | men...@wso2.com >>> >>> <https://wso2.com/signature> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Chashika Weerathunga* | Software Engineer | WSO2 Inc. >> (m) +94713731206 | Email: chash...@wso2.com >> [image: http://wso2.com] >> <http://wso2.com> >> _______________________________________________ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > > *Heshan Sudarshana* | Software Engineer | WSO2 Inc. > > Mobile: (+94)767006654 | Email: hesh...@wso2.com > [image: https://wso2.com/signature] <https://wso2.com/signature> > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Renuka Fernando* | Software Engineer | WSO2 Inc. (m) +9476 6678 752 | Email: ren...@wso2.com <http://wso2.com/signature>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
