Hi all,

Thank you very much for testing the WSO2 API Microgateway 3.2.0-RC2.

Since this vote has passed with 12 [+1]s and 0 [-1]s, we’re hereby closing
the vote and proceeding with the WSO2 API Microgateway 3.2.0 GA release.

Thanks and Regards,
Menaka



On Wed, Aug 26, 2020 at 1:30 PM Rivindu Madushan <[email protected]> wrote:

> Hi all,
>
> I have tested the Microgateway 3.2.0 RC2 toolkit and docker runtime for Open
> Banking use cases with CDS-AU mgw docker image. The following scenarios
> were covered.
> - Adding custom filters
> - Adding interceptors
> - Using a custom production endpoint.
> - Oauth flows
> - Ballerina interceptors
> - Use of deployment.toml
>
> No issues found
> *[+] Stable* - Go ahead and release
>
> Thanks
> Rivindu
>
> On Wed, Aug 26, 2020 at 1:08 PM Nadee Poornima <[email protected]> wrote:
>
>> Hi all,
>>
>> [resending as earlier email got blocked]
>>
>> 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.
>>>
>>
>> I have created a doc issue[1] to add the migration process for MGW
>> product. Appreciate to fix this issue before releasing the product.
>>
>> [1]. https://github.com/wso2/docs-mg/issues/38
>>
>> Cheers,
>> Nadee
>>
>> On Wed, Aug 26, 2020 at 1:06 PM Malintha Amarasinghe <[email protected]>
>> wrote:
>>
>>> Hi all,
>>> [resending as earlier email got blocked]
>>>
>>> Tested followings,
>>>
>>> 1. Binary QSG
>>> 2. API Key and OAuth Authentication
>>> 3. Mutual SSL for client
>>> 4. Importing an API from API Manager and building a MicroGW, invoking
>>> with OAuth Token
>>>
>>> No blockers found.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> Thanks!
>>>
>>> On Wed, Aug 26, 2020 at 11:54 AM Shalki Wenushika <[email protected]>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Tested followings,
>>>>
>>>>    - Testing on windows
>>>>    - Schema validation
>>>>    - Disable security for APIs
>>>>
>>>> No blockers found.
>>>>
>>>> *[+] Stable - Go ahead and release*
>>>>
>>>> Thanks,
>>>> Shalki.
>>>> *Shalki Wenushika *| Software Engineer | WSO2 Inc.
>>>> (m) +94716792399 | (e) [email protected]
>>>> <http://wso2.com/signature>
>>>>
>>>>
>>>> On Tue, Aug 25, 2020 at 10:06 PM Praminda Jayawardana <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Tested followings,
>>>>>
>>>>>    - Docker QSG
>>>>>    - Per API mutual ssl
>>>>>    - Compatibility with apictl
>>>>>    - JWT/Opaque token revocation
>>>>>    - Kubernetes artifact generation and functionality
>>>>>    - Service discovery with etcd
>>>>>    - Compatibility with WSO2 APIM 2.6.0
>>>>>    - Basic auth protected backend
>>>>>    - Basic auth authentication
>>>>>
>>>>> No blockers found.
>>>>>
>>>>> *[+] Stable - Go ahead and release*
>>>>>
>>>>> Thanks,
>>>>> Praminda
>>>>>
>>>>> On Tue, Aug 25, 2020 at 2:39 PM Heshan Sudarshana <[email protected]>
>>>>> 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 <
>>>>>> [email protected]> 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 <[email protected]>
>>>>>>> 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 <[email protected]>
>>>>>>>> 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 <
>>>>>>>>> [email protected]> 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 <
>>>>>>>>>> [email protected]> 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 <[email protected]>
>>>>>>>>>>> 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 <
>>>>>>>>>>>> [email protected]> 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 | [email protected]
>>>>>>>>>>>>>
>>>>>>>>>>>>> <https://wso2.com/signature>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Nadee Poornima*
>>>>>>>>>>>> Software Engineer | WSO2
>>>>>>>>>>>>
>>>>>>>>>>>> Email : [email protected]
>>>>>>>>>>>> Mobile : +94713441341
>>>>>>>>>>>> MyBlog: https://medium.com/nadees-tech-stories
>>>>>>>>>>>>
>>>>>>>>>>>> <https://wso2.com/signature>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Menaka Jayawardena*
>>>>>>>>>>> Senior Software Engineer *|* *WSO2* *Inc*.
>>>>>>>>>>> +94 71 350 5470 | [email protected]
>>>>>>>>>>>
>>>>>>>>>>> <https://wso2.com/signature>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Dev mailing list
>>>>>>>>>>> [email protected]
>>>>>>>>>>> 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 : [email protected]
>>>>>>>>> Mobile : +94713441341
>>>>>>>>> MyBlog: https://medium.com/nadees-tech-stories
>>>>>>>>>
>>>>>>>>> <https://wso2.com/signature>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Menaka Jayawardena*
>>>>>>>> Senior Software Engineer *|* *WSO2* *Inc*.
>>>>>>>> +94 71 350 5470 | [email protected]
>>>>>>>>
>>>>>>>> <https://wso2.com/signature>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Dev mailing list
>>>>>>>> [email protected]
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Chashika Weerathunga* | Software Engineer | WSO2 Inc.
>>>>>>> (m) +94713731206 | Email: [email protected]
>>>>>>> [image: http://wso2.com]
>>>>>>> <http://wso2.com>
>>>>>>> _______________________________________________
>>>>>>> Architecture mailing list
>>>>>>> [email protected]
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Heshan Sudarshana* | Software Engineer | WSO2 Inc.
>>>>>>
>>>>>> Mobile: (+94)767006654 | Email: [email protected]
>>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>> --
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>>
>>>>>> *Praminda Jayawardana* | Associate Technical Lead | WSO2 Inc.
>>>>>> <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> (e) <https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture>
>>>>>> [email protected]
>>>>>>
>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>
>>>>> GET INTEGRATION AGILE
>>>>> Integration Agility for Digitally Driven Business
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>
>>
>> --
>> *Nadee Poornima*
>> Software Engineer | WSO2
>>
>> Email : [email protected]
>> Mobile : +94713441341
>> MyBlog: https://medium.com/nadees-tech-stories
>>
>> <https://wso2.com/signature>
>>
>
>
> --
> *Rivindu Madushan *| Software Engineer | WSO2 Inc.
> (m) +94 71 765 7701 | (e) [email protected]
> <https://wso2.com/signature>
>


-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | [email protected]

<https://wso2.com/signature>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to