Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Naduni Pamudika]

Hi All,

Thank you for testing the RC2 of WSO2 API Manager Tooling 3.2.0 version.

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

Thanks,
Naduni

On Wed, Aug 26, 2020 at 2:19 PM Uvindra Dias Jayasinha 
wrote:

> Tested the following,
>
>- Exporting/import APIs, API Products, Apps.
>- Environment specific parameters
>- Dynamic data scenarios
>
> *[+] Stable - Go ahead and release*
>
> On Tue, 25 Aug 2020 at 15:45, Naduni Pamudika  wrote:
>
>> Hi All,
>>
>> Tested the following with API Manager Tooling 3.2.0 RC2 with API Manager
>> 3.2.0 RC6 in the Linux environment.
>>
>>- Export/Import APIs, Applications and API Products from/to different
>>APIM environments with latest APICTL.
>>- Generate keys with APICTL.
>>- Delete APIs, Applications (with keys, subscriptions) and API
>>Products in APIM via APICTL.
>>- Change the lifecycle status of an API deployed in APIM via APICTL.
>>
>> No blockers found.
>> +1 to proceed with the release.
>>
>> On Tue, Aug 25, 2020 at 10:16 AM Lakshitha Gunasekara 
>> wrote:
>>
>>> Hi All,
>>>
>>> Tested the following in APICTL 3.2.0-rc2 with WSO2 APIM 3.2.0-rc6.
>>>
>>>
>>>1. Setting up environments (add/remove/listing)
>>>2. API import with vcs deploy.
>>>3. API/APP listing with limit parameters and searching with the
>>>query parameters.
>>>4. Formating the listing outputs to different formats.
>>>5. Working with CA-signed certificates directly imported from the OS.
>>>
>>> No blockers found. +1 to proceed with the release.
>>>
>>> Thanks,
>>> Lakshitha
>>>
>>>
>>> On Tue, Aug 25, 2020 at 9:49 AM Shehani Rathnayake 
>>> wrote:
>>>
 Hi All,

 Tested the following in APICTL 3.2.0 - RC2, APIM 3.2.0 RC5.

 1. Setting up/ listing and removing environments.
 2. Importing and Exporting APIs
 3. Install/ Uninstall api-operator
 4. Kubernetes mode.
 5. Add/Update/Delete APIs in Kubernetes cluster.

 No blockers found.

 *[+] Stable - Go ahead and release.*

 Thanks.

 On Tue, Aug 25, 2020 at 9:39 AM Hiranya Abeyrathne 
 wrote:

> Hi all,
>
> Tested the following in APICTL 3.2.0 - RC2.
>
>
> 1. Setting up environments (add/remove/listing)
> 2. API/APP import/export and updating
> 3. API listing and searching
> 4. API Product support basic functionalities
> 5. Configuring environment specific params
> 6. Lifecycle update of deployed API
>
> No blockers found.
>
> [+ Stable] +1 to proceed with the release.
>
> Thanks!
> Hiranya Abeyrathne
> Software Engineer,
>
> *WSO2, Inc. *
>
> lean. enterprise. middleware
> Mob: +94 70210 8657
> LinkedIn: https://www.linkedin.com/in/hiranya-kavishani/
>
> 
>
>
> On Sat, Aug 22, 2020 at 12:55 PM Praminda Jayawardana <
> prami...@wso2.com> wrote:
>
>> Tested pushing Microgateway APIs to API Manager using apictl.
>> Tested compatibility of x-wso2 extensions.
>>
>> Didn't find any blockers.
>>
>> *[+] Stable - Go ahead and release.*
>>
>> On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
>> wrote:
>>
>>> Hi all,
>>>
>>> I tested the following scenarios with APIM 3.2.0 RC5.
>>>
>>>- Support for API Products from API Controller. (Tested with the
>>>following users)
>>>- Super tenant and tenant users with *Internal/devops* role
>>>   (which was newly introduced in APIM 3.2.0)
>>>   - Super tenant and tenant users with *admin* role
>>>   - Super tenant and tenant users who do not have full
>>>   privileges
>>>   - Test scenarios basically include the following.
>>>  - Import an API Product
>>>  - Export an API Product
>>>  - Generate Keys for an API Product
>>>  - Delete an API Product
>>>  - List API Products
>>>   - Support for Different Endpoint Types from API Controller.
>>>   - HTTP/REST (including load balancing and failover policies)
>>>   - HTTP/SOAP (including load balancing and failover policies)
>>>   - Dynamic
>>>   - AWS Lambda
>>>- GIT Integration with API Controller. (Tested the primary use
>>>cases associated with the following commands.)
>>>- apictl vcs init command
>>>   - apictl vcs status command
>>>   - apictl vcs deploy command (with APIs, API Products and
>>>   Applications)
>>>   - apictl set --vcs-deletion-enabled=true command and related
>>>   use cases
>>>   - apictl set --vcs-config-path /home/foo/vcs-config.yaml
>>>   commanf and related use cases
>>>   - Configuring Environment Specific Parameters
>>>- List Environments, APIs 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Uvindra Dias Jayasinha]

Tested the following,

   - Exporting/import APIs, API Products, Apps.
   - Environment specific parameters
   - Dynamic data scenarios

*[+] Stable - Go ahead and release*

On Tue, 25 Aug 2020 at 15:45, Naduni Pamudika  wrote:

> Hi All,
>
> Tested the following with API Manager Tooling 3.2.0 RC2 with API Manager
> 3.2.0 RC6 in the Linux environment.
>
>- Export/Import APIs, Applications and API Products from/to different
>APIM environments with latest APICTL.
>- Generate keys with APICTL.
>- Delete APIs, Applications (with keys, subscriptions) and API
>Products in APIM via APICTL.
>- Change the lifecycle status of an API deployed in APIM via APICTL.
>
> No blockers found.
> +1 to proceed with the release.
>
> On Tue, Aug 25, 2020 at 10:16 AM Lakshitha Gunasekara 
> wrote:
>
>> Hi All,
>>
>> Tested the following in APICTL 3.2.0-rc2 with WSO2 APIM 3.2.0-rc6.
>>
>>
>>1. Setting up environments (add/remove/listing)
>>2. API import with vcs deploy.
>>3. API/APP listing with limit parameters and searching with the query
>>parameters.
>>4. Formating the listing outputs to different formats.
>>5. Working with CA-signed certificates directly imported from the OS.
>>
>> No blockers found. +1 to proceed with the release.
>>
>> Thanks,
>> Lakshitha
>>
>>
>> On Tue, Aug 25, 2020 at 9:49 AM Shehani Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> Tested the following in APICTL 3.2.0 - RC2, APIM 3.2.0 RC5.
>>>
>>> 1. Setting up/ listing and removing environments.
>>> 2. Importing and Exporting APIs
>>> 3. Install/ Uninstall api-operator
>>> 4. Kubernetes mode.
>>> 5. Add/Update/Delete APIs in Kubernetes cluster.
>>>
>>> No blockers found.
>>>
>>> *[+] Stable - Go ahead and release.*
>>>
>>> Thanks.
>>>
>>> On Tue, Aug 25, 2020 at 9:39 AM Hiranya Abeyrathne 
>>> wrote:
>>>
 Hi all,

 Tested the following in APICTL 3.2.0 - RC2.


 1. Setting up environments (add/remove/listing)
 2. API/APP import/export and updating
 3. API listing and searching
 4. API Product support basic functionalities
 5. Configuring environment specific params
 6. Lifecycle update of deployed API

 No blockers found.

 [+ Stable] +1 to proceed with the release.

 Thanks!
 Hiranya Abeyrathne
 Software Engineer,

 *WSO2, Inc. *

 lean. enterprise. middleware
 Mob: +94 70210 8657
 LinkedIn: https://www.linkedin.com/in/hiranya-kavishani/

 


 On Sat, Aug 22, 2020 at 12:55 PM Praminda Jayawardana <
 prami...@wso2.com> wrote:

> Tested pushing Microgateway APIs to API Manager using apictl.
> Tested compatibility of x-wso2 extensions.
>
> Didn't find any blockers.
>
> *[+] Stable - Go ahead and release.*
>
> On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
> wrote:
>
>> Hi all,
>>
>> I tested the following scenarios with APIM 3.2.0 RC5.
>>
>>- Support for API Products from API Controller. (Tested with the
>>following users)
>>- Super tenant and tenant users with *Internal/devops* role
>>   (which was newly introduced in APIM 3.2.0)
>>   - Super tenant and tenant users with *admin* role
>>   - Super tenant and tenant users who do not have full privileges
>>   - Test scenarios basically include the following.
>>  - Import an API Product
>>  - Export an API Product
>>  - Generate Keys for an API Product
>>  - Delete an API Product
>>  - List API Products
>>   - Support for Different Endpoint Types from API Controller.
>>   - HTTP/REST (including load balancing and failover policies)
>>   - HTTP/SOAP (including load balancing and failover policies)
>>   - Dynamic
>>   - AWS Lambda
>>- GIT Integration with API Controller. (Tested the primary use
>>cases associated with the following commands.)
>>- apictl vcs init command
>>   - apictl vcs status command
>>   - apictl vcs deploy command (with APIs, API Products and
>>   Applications)
>>   - apictl set --vcs-deletion-enabled=true command and related
>>   use cases
>>   - apictl set --vcs-config-path /home/foo/vcs-config.yaml
>>   commanf and related use cases
>>   - Configuring Environment Specific Parameters
>>- List Environments, APIs and Applications
>>- Generate Keys for an API
>>- Initialize an API (including the dev first approach)
>>
>> Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251
>>
>> No blockers found.
>>
>> *[+] Stable - Go ahead and release.*
>>
>> Thanks,
>> Wasura
>>
>> On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following in APICTL 3.2.0 - RC2 with 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Naduni Pamudika]

Hi All,

Tested the following with API Manager Tooling 3.2.0 RC2 with API Manager
3.2.0 RC6 in the Linux environment.

   - Export/Import APIs, Applications and API Products from/to different
   APIM environments with latest APICTL.
   - Generate keys with APICTL.
   - Delete APIs, Applications (with keys, subscriptions) and API Products
   in APIM via APICTL.
   - Change the lifecycle status of an API deployed in APIM via APICTL.

No blockers found.
+1 to proceed with the release.

On Tue, Aug 25, 2020 at 10:16 AM Lakshitha Gunasekara 
wrote:

> Hi All,
>
> Tested the following in APICTL 3.2.0-rc2 with WSO2 APIM 3.2.0-rc6.
>
>
>1. Setting up environments (add/remove/listing)
>2. API import with vcs deploy.
>3. API/APP listing with limit parameters and searching with the query
>parameters.
>4. Formating the listing outputs to different formats.
>5. Working with CA-signed certificates directly imported from the OS.
>
> No blockers found. +1 to proceed with the release.
>
> Thanks,
> Lakshitha
>
>
> On Tue, Aug 25, 2020 at 9:49 AM Shehani Rathnayake 
> wrote:
>
>> Hi All,
>>
>> Tested the following in APICTL 3.2.0 - RC2, APIM 3.2.0 RC5.
>>
>> 1. Setting up/ listing and removing environments.
>> 2. Importing and Exporting APIs
>> 3. Install/ Uninstall api-operator
>> 4. Kubernetes mode.
>> 5. Add/Update/Delete APIs in Kubernetes cluster.
>>
>> No blockers found.
>>
>> *[+] Stable - Go ahead and release.*
>>
>> Thanks.
>>
>> On Tue, Aug 25, 2020 at 9:39 AM Hiranya Abeyrathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested the following in APICTL 3.2.0 - RC2.
>>>
>>>
>>> 1. Setting up environments (add/remove/listing)
>>> 2. API/APP import/export and updating
>>> 3. API listing and searching
>>> 4. API Product support basic functionalities
>>> 5. Configuring environment specific params
>>> 6. Lifecycle update of deployed API
>>>
>>> No blockers found.
>>>
>>> [+ Stable] +1 to proceed with the release.
>>>
>>> Thanks!
>>> Hiranya Abeyrathne
>>> Software Engineer,
>>>
>>> *WSO2, Inc. *
>>>
>>> lean. enterprise. middleware
>>> Mob: +94 70210 8657
>>> LinkedIn: https://www.linkedin.com/in/hiranya-kavishani/
>>>
>>> 
>>>
>>>
>>> On Sat, Aug 22, 2020 at 12:55 PM Praminda Jayawardana 
>>> wrote:
>>>
 Tested pushing Microgateway APIs to API Manager using apictl.
 Tested compatibility of x-wso2 extensions.

 Didn't find any blockers.

 *[+] Stable - Go ahead and release.*

 On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
 wrote:

> Hi all,
>
> I tested the following scenarios with APIM 3.2.0 RC5.
>
>- Support for API Products from API Controller. (Tested with the
>following users)
>- Super tenant and tenant users with *Internal/devops* role (which
>   was newly introduced in APIM 3.2.0)
>   - Super tenant and tenant users with *admin* role
>   - Super tenant and tenant users who do not have full privileges
>   - Test scenarios basically include the following.
>  - Import an API Product
>  - Export an API Product
>  - Generate Keys for an API Product
>  - Delete an API Product
>  - List API Products
>   - Support for Different Endpoint Types from API Controller.
>   - HTTP/REST (including load balancing and failover policies)
>   - HTTP/SOAP (including load balancing and failover policies)
>   - Dynamic
>   - AWS Lambda
>- GIT Integration with API Controller. (Tested the primary use
>cases associated with the following commands.)
>- apictl vcs init command
>   - apictl vcs status command
>   - apictl vcs deploy command (with APIs, API Products and
>   Applications)
>   - apictl set --vcs-deletion-enabled=true command and related
>   use cases
>   - apictl set --vcs-config-path /home/foo/vcs-config.yaml
>   commanf and related use cases
>   - Configuring Environment Specific Parameters
>- List Environments, APIs and Applications
>- Generate Keys for an API
>- Initialize an API (including the dev first approach)
>
> Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251
>
> No blockers found.
>
> *[+] Stable - Go ahead and release.*
>
> Thanks,
> Wasura
>
> On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara 
> wrote:
>
>> Hi all,
>>
>> I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.
>>
>>- Manage Environments (add/remove/list environments) and log in
>>using email as the username.
>>- List APIs/Applications using a super tenant/tenant users and as
>>DevOps User.
>>- Initialize an API without any flag, with the definition.yaml
>>and using from OpenAPI/Swagger Specification
>>- Set commands (Change 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Lakshitha Gunasekara]

Hi All,

Tested the following in APICTL 3.2.0-rc2 with WSO2 APIM 3.2.0-rc6.


   1. Setting up environments (add/remove/listing)
   2. API import with vcs deploy.
   3. API/APP listing with limit parameters and searching with the query
   parameters.
   4. Formating the listing outputs to different formats.
   5. Working with CA-signed certificates directly imported from the OS.

No blockers found. +1 to proceed with the release.

Thanks,
Lakshitha


On Tue, Aug 25, 2020 at 9:49 AM Shehani Rathnayake 
wrote:

> Hi All,
>
> Tested the following in APICTL 3.2.0 - RC2, APIM 3.2.0 RC5.
>
> 1. Setting up/ listing and removing environments.
> 2. Importing and Exporting APIs
> 3. Install/ Uninstall api-operator
> 4. Kubernetes mode.
> 5. Add/Update/Delete APIs in Kubernetes cluster.
>
> No blockers found.
>
> *[+] Stable - Go ahead and release.*
>
> Thanks.
>
> On Tue, Aug 25, 2020 at 9:39 AM Hiranya Abeyrathne 
> wrote:
>
>> Hi all,
>>
>> Tested the following in APICTL 3.2.0 - RC2.
>>
>>
>> 1. Setting up environments (add/remove/listing)
>> 2. API/APP import/export and updating
>> 3. API listing and searching
>> 4. API Product support basic functionalities
>> 5. Configuring environment specific params
>> 6. Lifecycle update of deployed API
>>
>> No blockers found.
>>
>> [+ Stable] +1 to proceed with the release.
>>
>> Thanks!
>> Hiranya Abeyrathne
>> Software Engineer,
>>
>> *WSO2, Inc. *
>>
>> lean. enterprise. middleware
>> Mob: +94 70210 8657
>> LinkedIn: https://www.linkedin.com/in/hiranya-kavishani/
>>
>> 
>>
>>
>> On Sat, Aug 22, 2020 at 12:55 PM Praminda Jayawardana 
>> wrote:
>>
>>> Tested pushing Microgateway APIs to API Manager using apictl.
>>> Tested compatibility of x-wso2 extensions.
>>>
>>> Didn't find any blockers.
>>>
>>> *[+] Stable - Go ahead and release.*
>>>
>>> On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
>>> wrote:
>>>
 Hi all,

 I tested the following scenarios with APIM 3.2.0 RC5.

- Support for API Products from API Controller. (Tested with the
following users)
- Super tenant and tenant users with *Internal/devops* role (which
   was newly introduced in APIM 3.2.0)
   - Super tenant and tenant users with *admin* role
   - Super tenant and tenant users who do not have full privileges
   - Test scenarios basically include the following.
  - Import an API Product
  - Export an API Product
  - Generate Keys for an API Product
  - Delete an API Product
  - List API Products
   - Support for Different Endpoint Types from API Controller.
   - HTTP/REST (including load balancing and failover policies)
   - HTTP/SOAP (including load balancing and failover policies)
   - Dynamic
   - AWS Lambda
- GIT Integration with API Controller. (Tested the primary use
cases associated with the following commands.)
- apictl vcs init command
   - apictl vcs status command
   - apictl vcs deploy command (with APIs, API Products and
   Applications)
   - apictl set --vcs-deletion-enabled=true command and related use
   cases
   - apictl set --vcs-config-path /home/foo/vcs-config.yaml commanf
   and related use cases
   - Configuring Environment Specific Parameters
- List Environments, APIs and Applications
- Generate Keys for an API
- Initialize an API (including the dev first approach)

 Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251

 No blockers found.

 *[+] Stable - Go ahead and release.*

 Thanks,
 Wasura

 On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara 
 wrote:

> Hi all,
>
> I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.
>
>- Manage Environments (add/remove/list environments) and log in
>using email as the username.
>- List APIs/Applications using a super tenant/tenant users and as
>DevOps User.
>- Initialize an API without any flag, with the definition.yaml and
>using from OpenAPI/Swagger Specification
>- Set commands (Change export-directory)
>- Import API (as Admin and Devops user, using a secondary user
>store as well, importing GraphQL APIs,  SOAP service as a REST APIs and
>APIS with documentations and thumbnails)
>- Import API-Products (as Admin and Devops user, using a secondary
>user store as well, Cross tenants import and with different 
> combinations of
>optional flags)
>- Update an existing API by importing it again  with different
>endpoint configs for prod and dev environments (with --update flag)
>- Update the documentation and thumbnails of APIs  by importing it
>again  (with --update flag)
>- Export API (as Admin and Devops 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Hiranya Abeyrathne]

Hi all,

Tested the following in APICTL 3.2.0 - RC2.


1. Setting up environments (add/remove/listing)
2. API/APP import/export and updating
3. API listing and searching
4. API Product support basic functionalities
5. Configuring environment specific params
6. Lifecycle update of deployed API

No blockers found.

[+ Stable] +1 to proceed with the release.

Thanks!
Hiranya Abeyrathne
Software Engineer,

*WSO2, Inc. *

lean. enterprise. middleware
Mob: +94 70210 8657
LinkedIn: https://www.linkedin.com/in/hiranya-kavishani/




On Sat, Aug 22, 2020 at 12:55 PM Praminda Jayawardana 
wrote:

> Tested pushing Microgateway APIs to API Manager using apictl.
> Tested compatibility of x-wso2 extensions.
>
> Didn't find any blockers.
>
> *[+] Stable - Go ahead and release.*
>
> On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
> wrote:
>
>> Hi all,
>>
>> I tested the following scenarios with APIM 3.2.0 RC5.
>>
>>- Support for API Products from API Controller. (Tested with the
>>following users)
>>- Super tenant and tenant users with *Internal/devops* role (which
>>   was newly introduced in APIM 3.2.0)
>>   - Super tenant and tenant users with *admin* role
>>   - Super tenant and tenant users who do not have full privileges
>>   - Test scenarios basically include the following.
>>  - Import an API Product
>>  - Export an API Product
>>  - Generate Keys for an API Product
>>  - Delete an API Product
>>  - List API Products
>>   - Support for Different Endpoint Types from API Controller.
>>   - HTTP/REST (including load balancing and failover policies)
>>   - HTTP/SOAP (including load balancing and failover policies)
>>   - Dynamic
>>   - AWS Lambda
>>- GIT Integration with API Controller. (Tested the primary use cases
>>associated with the following commands.)
>>- apictl vcs init command
>>   - apictl vcs status command
>>   - apictl vcs deploy command (with APIs, API Products and
>>   Applications)
>>   - apictl set --vcs-deletion-enabled=true command and related use
>>   cases
>>   - apictl set --vcs-config-path /home/foo/vcs-config.yaml commanf
>>   and related use cases
>>   - Configuring Environment Specific Parameters
>>- List Environments, APIs and Applications
>>- Generate Keys for an API
>>- Initialize an API (including the dev first approach)
>>
>> Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251
>>
>> No blockers found.
>>
>> *[+] Stable - Go ahead and release.*
>>
>> Thanks,
>> Wasura
>>
>> On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.
>>>
>>>- Manage Environments (add/remove/list environments) and log in
>>>using email as the username.
>>>- List APIs/Applications using a super tenant/tenant users and as
>>>DevOps User.
>>>- Initialize an API without any flag, with the definition.yaml and
>>>using from OpenAPI/Swagger Specification
>>>- Set commands (Change export-directory)
>>>- Import API (as Admin and Devops user, using a secondary user store
>>>as well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS 
>>> with
>>>documentations and thumbnails)
>>>- Import API-Products (as Admin and Devops user, using a secondary
>>>user store as well, Cross tenants import and with different combinations 
>>> of
>>>optional flags)
>>>- Update an existing API by importing it again  with different
>>>endpoint configs for prod and dev environments (with --update flag)
>>>- Update the documentation and thumbnails of APIs  by importing it
>>>again  (with --update flag)
>>>- Export API (as Admin and Devops user, and across tenants, using a
>>>secondary user store as well, export GraphQL APIs,  SOAP service as a 
>>> REST
>>>APIs and APIs with documentation and thumbnails)
>>>- Change the lifecycle status of an API deployed in APIM via APICTL.
>>>(using a secondary store as well)
>>>- Delete API-products, Apis, Apps (as Admin and Devops user, and
>>>using a secondary store)
>>>- Import API-Products (as Admin and Devops user, using a secondary
>>>user store as well,)
>>>- Exporting all APIs of a tenant (with export-apis command)
>>>- Export App (as DevOps/admin users, for super tenant/ tenant users
>>>also with subscriptions and keys)
>>>- Import App (as a directory and zip, and using a secondary user
>>>store)
>>>- Generating Keys (as DevOps/admin super tenant users, devop/admin
>>>tenant users, using a secondary user store as well for APIs and API
>>>products)
>>>- Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP
>>>endpoints with load-balanced and failover mechanisms, Dynamic endpoints,
>>>and AWS Lambda endpoints)
>>>
>>> Tested these scenarios in the  Windows 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Praminda Jayawardana]

Tested pushing Microgateway APIs to API Manager using apictl.
Tested compatibility of x-wso2 extensions.

Didn't find any blockers.

*[+] Stable - Go ahead and release.*

On Mon, Aug 17, 2020 at 7:53 PM Wasura Wattearachchi 
wrote:

> Hi all,
>
> I tested the following scenarios with APIM 3.2.0 RC5.
>
>- Support for API Products from API Controller. (Tested with the
>following users)
>- Super tenant and tenant users with *Internal/devops* role (which was
>   newly introduced in APIM 3.2.0)
>   - Super tenant and tenant users with *admin* role
>   - Super tenant and tenant users who do not have full privileges
>   - Test scenarios basically include the following.
>  - Import an API Product
>  - Export an API Product
>  - Generate Keys for an API Product
>  - Delete an API Product
>  - List API Products
>   - Support for Different Endpoint Types from API Controller.
>   - HTTP/REST (including load balancing and failover policies)
>   - HTTP/SOAP (including load balancing and failover policies)
>   - Dynamic
>   - AWS Lambda
>- GIT Integration with API Controller. (Tested the primary use cases
>associated with the following commands.)
>- apictl vcs init command
>   - apictl vcs status command
>   - apictl vcs deploy command (with APIs, API Products and
>   Applications)
>   - apictl set --vcs-deletion-enabled=true command and related use
>   cases
>   - apictl set --vcs-config-path /home/foo/vcs-config.yaml commanf
>   and related use cases
>   - Configuring Environment Specific Parameters
>- List Environments, APIs and Applications
>- Generate Keys for an API
>- Initialize an API (including the dev first approach)
>
> Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251
>
> No blockers found.
>
> *[+] Stable - Go ahead and release.*
>
> Thanks,
> Wasura
>
> On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara 
> wrote:
>
>> Hi all,
>>
>> I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.
>>
>>- Manage Environments (add/remove/list environments) and log in using
>>email as the username.
>>- List APIs/Applications using a super tenant/tenant users and as
>>DevOps User.
>>- Initialize an API without any flag, with the definition.yaml and
>>using from OpenAPI/Swagger Specification
>>- Set commands (Change export-directory)
>>- Import API (as Admin and Devops user, using a secondary user store
>>as well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS 
>> with
>>documentations and thumbnails)
>>- Import API-Products (as Admin and Devops user, using a secondary
>>user store as well, Cross tenants import and with different combinations 
>> of
>>optional flags)
>>- Update an existing API by importing it again  with different
>>endpoint configs for prod and dev environments (with --update flag)
>>- Update the documentation and thumbnails of APIs  by importing it
>>again  (with --update flag)
>>- Export API (as Admin and Devops user, and across tenants, using a
>>secondary user store as well, export GraphQL APIs,  SOAP service as a REST
>>APIs and APIs with documentation and thumbnails)
>>- Change the lifecycle status of an API deployed in APIM via APICTL.
>>(using a secondary store as well)
>>- Delete API-products, Apis, Apps (as Admin and Devops user, and
>>using a secondary store)
>>- Import API-Products (as Admin and Devops user, using a secondary
>>user store as well,)
>>- Exporting all APIs of a tenant (with export-apis command)
>>- Export App (as DevOps/admin users, for super tenant/ tenant users
>>also with subscriptions and keys)
>>- Import App (as a directory and zip, and using a secondary user
>>store)
>>- Generating Keys (as DevOps/admin super tenant users, devop/admin
>>tenant users, using a secondary user store as well for APIs and API
>>products)
>>- Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP
>>endpoints with load-balanced and failover mechanisms, Dynamic endpoints,
>>and AWS Lambda endpoints)
>>
>> Tested these scenarios in the  Windows Environment (Windows10 -64Bit-
>> 2005).
>>
>>
>> No blockers found.
>>
>> [+ Stable]
>>
>> +1 to proceed with the release.
>>
>> On Mon, Aug 17, 2020 at 10:07 AM Malintha Amarasinghe 
>> wrote:
>>
>>> Tested with APIM 3.2.0 RC5 and Ubuntu 18.04
>>>
>>> 1. API/App/Product import-export and updating
>>> 2. API listing, searching, and pagination
>>> 3. Using environment variables and per-env based endpoints using
>>> api_params.yaml
>>> 4. GIT Integration functionality
>>> 5. Generating Keys and invoking the APIs
>>> 6. Subscriptions and Keys provisioning
>>> 7. Ran the apictl integration test suit.
>>>
>>> No blockers found.
>>> [+ Stable]
>>> +1 to proceed with the release.
>>>
>>> Thanks!
>>>
>>>
>>> On Fri, Aug 14, 2020 at 6:26 PM 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Wasura Wattearachchi]

Hi all,

I tested the following scenarios with APIM 3.2.0 RC5.

   - Support for API Products from API Controller. (Tested with the
   following users)
   - Super tenant and tenant users with *Internal/devops* role (which was
  newly introduced in APIM 3.2.0)
  - Super tenant and tenant users with *admin* role
  - Super tenant and tenant users who do not have full privileges
  - Test scenarios basically include the following.
 - Import an API Product
 - Export an API Product
 - Generate Keys for an API Product
 - Delete an API Product
 - List API Products
  - Support for Different Endpoint Types from API Controller.
  - HTTP/REST (including load balancing and failover policies)
  - HTTP/SOAP (including load balancing and failover policies)
  - Dynamic
  - AWS Lambda
   - GIT Integration with API Controller. (Tested the primary use cases
   associated with the following commands.)
   - apictl vcs init command
  - apictl vcs status command
  - apictl vcs deploy command (with APIs, API Products and Applications)
  - apictl set --vcs-deletion-enabled=true command and related use cases
  - apictl set --vcs-config-path /home/foo/vcs-config.yaml commanf and
  related use cases
  - Configuring Environment Specific Parameters
   - List Environments, APIs and Applications
   - Generate Keys for an API
   - Initialize an API (including the dev first approach)

Testing environment - Ubuntu 20.04 LTS, JDK 1.8.0_251

No blockers found.

*[+] Stable - Go ahead and release.*

Thanks,
Wasura

On Mon, Aug 17, 2020 at 10:56 AM Chamindu Udakara  wrote:

> Hi all,
>
> I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.
>
>- Manage Environments (add/remove/list environments) and log in using
>email as the username.
>- List APIs/Applications using a super tenant/tenant users and as
>DevOps User.
>- Initialize an API without any flag, with the definition.yaml and
>using from OpenAPI/Swagger Specification
>- Set commands (Change export-directory)
>- Import API (as Admin and Devops user, using a secondary user store
>as well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS with
>documentations and thumbnails)
>- Import API-Products (as Admin and Devops user, using a secondary
>user store as well, Cross tenants import and with different combinations of
>optional flags)
>- Update an existing API by importing it again  with different
>endpoint configs for prod and dev environments (with --update flag)
>- Update the documentation and thumbnails of APIs  by importing it
>again  (with --update flag)
>- Export API (as Admin and Devops user, and across tenants, using a
>secondary user store as well, export GraphQL APIs,  SOAP service as a REST
>APIs and APIs with documentation and thumbnails)
>- Change the lifecycle status of an API deployed in APIM via APICTL.
>(using a secondary store as well)
>- Delete API-products, Apis, Apps (as Admin and Devops user, and using
>a secondary store)
>- Import API-Products (as Admin and Devops user, using a secondary
>user store as well,)
>- Exporting all APIs of a tenant (with export-apis command)
>- Export App (as DevOps/admin users, for super tenant/ tenant users
>also with subscriptions and keys)
>- Import App (as a directory and zip, and using a secondary user store)
>- Generating Keys (as DevOps/admin super tenant users, devop/admin
>tenant users, using a secondary user store as well for APIs and API
>products)
>- Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP endpoints
>with load-balanced and failover mechanisms, Dynamic endpoints, and AWS
>Lambda endpoints)
>
> Tested these scenarios in the  Windows Environment (Windows10 -64Bit-
> 2005).
>
>
> No blockers found.
>
> [+ Stable]
>
> +1 to proceed with the release.
>
> On Mon, Aug 17, 2020 at 10:07 AM Malintha Amarasinghe 
> wrote:
>
>> Tested with APIM 3.2.0 RC5 and Ubuntu 18.04
>>
>> 1. API/App/Product import-export and updating
>> 2. API listing, searching, and pagination
>> 3. Using environment variables and per-env based endpoints using
>> api_params.yaml
>> 4. GIT Integration functionality
>> 5. Generating Keys and invoking the APIs
>> 6. Subscriptions and Keys provisioning
>> 7. Ran the apictl integration test suit.
>>
>> No blockers found.
>> [+ Stable]
>> +1 to proceed with the release.
>>
>> Thanks!
>>
>>
>> On Fri, Aug 14, 2020 at 6:26 PM Renuka Fernando  wrote:
>>
>>> Hi all,
>>>
>>> Tested following in APICTL 3.2.0 - RC2
>>>
>>>1.
>>>
>>>Install API Operator
>>>-
>>>
>>>   Interactive mode
>>>   -
>>>
>>>   Batch mode
>>>   -
>>>
>>>   With -f 
>>>   -
>>>
>>>   DockerHub registry type
>>>   -
>>>
>>>   HTTP registry type
>>>   2.
>>>
>>>Uninstall API Operator
>>>3.
>>>
>>>Add an API in 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Chamindu Udakara]

Hi all,

I have tested the following in APICTL 3.2.0 - RC2 with APIM-3.2.0 RC5.

   - Manage Environments (add/remove/list environments) and log in using
   email as the username.
   - List APIs/Applications using a super tenant/tenant users and as DevOps
   User.
   - Initialize an API without any flag, with the definition.yaml and using
   from OpenAPI/Swagger Specification
   - Set commands (Change export-directory)
   - Import API (as Admin and Devops user, using a secondary user store as
   well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS with
   documentations and thumbnails)
   - Import API-Products (as Admin and Devops user, using a secondary user
   store as well, Cross tenants import and with different combinations of
   optional flags)
   - Update an existing API by importing it again  with different endpoint
   configs for prod and dev environments (with --update flag)
   - Update the documentation and thumbnails of APIs  by importing it again
(with --update flag)
   - Export API (as Admin and Devops user, and across tenants, using a
   secondary user store as well, export GraphQL APIs,  SOAP service as a REST
   APIs and APIs with documentation and thumbnails)
   - Change the lifecycle status of an API deployed in APIM via APICTL.
   (using a secondary store as well)
   - Delete API-products, Apis, Apps (as Admin and Devops user, and using a
   secondary store)
   - Import API-Products (as Admin and Devops user, using a secondary user
   store as well,)
   - Exporting all APIs of a tenant (with export-apis command)
   - Export App (as DevOps/admin users, for super tenant/ tenant users also
   with subscriptions and keys)
   - Import App (as a directory and zip, and using a secondary user store)
   - Generating Keys (as DevOps/admin super tenant users, devop/admin
   tenant users, using a secondary user store as well for APIs and API
   products)
   - Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP endpoints
   with load-balanced and failover mechanisms, Dynamic endpoints, and AWS
   Lambda endpoints)

Tested these scenarios in the  Windows Environment (Windows10 -64Bit- 2005).


No blockers found.

[+ Stable]

+1 to proceed with the release.

On Mon, Aug 17, 2020 at 10:07 AM Malintha Amarasinghe 
wrote:

> Tested with APIM 3.2.0 RC5 and Ubuntu 18.04
>
> 1. API/App/Product import-export and updating
> 2. API listing, searching, and pagination
> 3. Using environment variables and per-env based endpoints using
> api_params.yaml
> 4. GIT Integration functionality
> 5. Generating Keys and invoking the APIs
> 6. Subscriptions and Keys provisioning
> 7. Ran the apictl integration test suit.
>
> No blockers found.
> [+ Stable]
> +1 to proceed with the release.
>
> Thanks!
>
>
> On Fri, Aug 14, 2020 at 6:26 PM Renuka Fernando  wrote:
>
>> Hi all,
>>
>> Tested following in APICTL 3.2.0 - RC2
>>
>>1.
>>
>>Install API Operator
>>-
>>
>>   Interactive mode
>>   -
>>
>>   Batch mode
>>   -
>>
>>   With -f 
>>   -
>>
>>   DockerHub registry type
>>   -
>>
>>   HTTP registry type
>>   2.
>>
>>Uninstall API Operator
>>3.
>>
>>Add an API in K8s cluster
>>4.
>>
>>Update an existing API in K8s cluster
>>5.
>>
>>Add/remove environment
>>6.
>>
>>Initialize API
>>7.
>>
>>Delete API in K8s cluster with given name and with from-file flag.
>>8.
>>
>>Basic kubectl commands
>>
>>
>> Tested these scenarios in macOs Catalina (version 10.15.6), kubectl
>> version v1.17.3
>>
>> No blockers found.
>>
>> [+ Stable]
>>
>> +1 to proceed with the release.
>>
>>
>> Thanks,
>>
>> Renuka
>>
>> On Fri, Aug 14, 2020 at 12:49 PM Chamindu Udakara 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following in APICTL 3.2.0 - RC2.
>>>
>>>
>>>-
>>>
>>>Manage Environments (add/remove/list environments) and log in using
>>>email as the username.
>>>-
>>>
>>>List APIs/Applications using a super tenant/tenant users and as
>>>DevOps User.
>>>-
>>>
>>>Initialize an API without any flag, with the definition.yaml and
>>>using from OpenAPI/Swagger Specification
>>>-
>>>
>>>Set commands (Change export-directory)
>>>-
>>>
>>>Import API (as Admin and Devops user, using a secondary user store
>>>as well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS 
>>> with
>>>documentations and thumbnails)
>>>-
>>>
>>>Import API-Products (as Admin and Devops user, using a secondary
>>>user store as well, Cross tenants import and with different combinations 
>>> of
>>>optional flags)
>>>-
>>>
>>>Update an existing API by importing it again  with different
>>>endpoint configs for prod and dev environments (with --update flag)
>>>-
>>>
>>>Update the documentation and thumbnails of APIs  by importing it
>>>again  (with --update flag)
>>>-
>>>
>>>Export API (as Admin and Devops user, and across tenants, using a

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Malintha Amarasinghe]

Tested with APIM 3.2.0 RC5 and Ubuntu 18.04

1. API/App/Product import-export and updating
2. API listing, searching, and pagination
3. Using environment variables and per-env based endpoints using
api_params.yaml
4. GIT Integration functionality
5. Generating Keys and invoking the APIs
6. Subscriptions and Keys provisioning
7. Ran the apictl integration test suit.

No blockers found.
[+ Stable]
+1 to proceed with the release.

Thanks!


On Fri, Aug 14, 2020 at 6:26 PM Renuka Fernando  wrote:

> Hi all,
>
> Tested following in APICTL 3.2.0 - RC2
>
>1.
>
>Install API Operator
>-
>
>   Interactive mode
>   -
>
>   Batch mode
>   -
>
>   With -f 
>   -
>
>   DockerHub registry type
>   -
>
>   HTTP registry type
>   2.
>
>Uninstall API Operator
>3.
>
>Add an API in K8s cluster
>4.
>
>Update an existing API in K8s cluster
>5.
>
>Add/remove environment
>6.
>
>Initialize API
>7.
>
>Delete API in K8s cluster with given name and with from-file flag.
>8.
>
>Basic kubectl commands
>
>
> Tested these scenarios in macOs Catalina (version 10.15.6), kubectl
> version v1.17.3
>
> No blockers found.
>
> [+ Stable]
>
> +1 to proceed with the release.
>
>
> Thanks,
>
> Renuka
>
> On Fri, Aug 14, 2020 at 12:49 PM Chamindu Udakara 
> wrote:
>
>> Hi all,
>>
>> I have tested the following in APICTL 3.2.0 - RC2.
>>
>>
>>-
>>
>>Manage Environments (add/remove/list environments) and log in using
>>email as the username.
>>-
>>
>>List APIs/Applications using a super tenant/tenant users and as
>>DevOps User.
>>-
>>
>>Initialize an API without any flag, with the definition.yaml and
>>using from OpenAPI/Swagger Specification
>>-
>>
>>Set commands (Change export-directory)
>>-
>>
>>Import API (as Admin and Devops user, using a secondary user store as
>>well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS with
>>documentations and thumbnails)
>>-
>>
>>Import API-Products (as Admin and Devops user, using a secondary user
>>store as well, Cross tenants import and with different combinations of
>>optional flags)
>>-
>>
>>Update an existing API by importing it again  with different endpoint
>>configs for prod and dev environments (with --update flag)
>>-
>>
>>Update the documentation and thumbnails of APIs  by importing it
>>again  (with --update flag)
>>-
>>
>>Export API (as Admin and Devops user, and across tenants, using a
>>secondary user store as well, export GraphQL APIs,  SOAP service as a REST
>>APIs and APIs with documentation and thumbnails)
>>-
>>
>>Change the lifecycle status of an API deployed in APIM via APICTL.
>>(using a secondary store as well)
>>-
>>
>>Delete API-products, Apis, Apps (as Admin and Devops user, and using
>>a secondary store)
>>-
>>
>>Import API-Products (as Admin and Devops user, using a secondary user
>>store as well,)
>>-
>>
>>Exporting all APIs of a tenant (with export-apis command)
>>-
>>
>>Export App (as DevOps/admin users, for super tenant/ tenant users
>>also with subscriptions and keys)
>>-
>>
>>Import App (as a directory and zip, and using a secondary user store)
>>-
>>
>>Generating Keys (as DevOps/admin super tenant users, devop/admin
>>tenant users, using a secondary user store as well for APIs and API
>>products)
>>-
>>
>>Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP endpoints
>>with load-balanced and failover mechanisms, Dynamic endpoints, and AWS
>>Lambda endpoints)
>>
>>
>> Tested these scenarios in the Linux environment (Ubuntu 20.04) and
>> Windows Environment (Windows10 -64Bit- 2005)
>>
>> No blockers found.
>>
>> [+ Stable]
>>
>> +1 to proceed with the release.
>>
>>
>>
>> On Thu, Aug 13, 2020 at 11:35 PM Naduni Pamudika  wrote:
>>
>>> Hi All,
>>>
>>> WSO2 Api Manager team is pleased to announce the second release
>>> candidate of WSO2 API Manager Tooling 3.2.0 version.
>>>
>>> The WSO2 API Manager tooling provides the capability to import and
>>> export APIs, Applications and API Products across multiple environments
>>> seamlessly. Hence it provides greater flexibility to create CI/CD pipelines
>>> for APIs, Applications and API Products.
>>>
>>> Apart from migrating APIs, Applications and API Products, it supports
>>> Kubernetes API operator to deploy and manage APIs in the Kubernetes cluster
>>> by reducing additional overheads for the DevOps.
>>>
>>> Please find the new features, improvements and fixes related to this
>>> release in  the following links.
>>> New Features
>>> 
>>> Fixed Issues
>>> 
>>>
>>> Download the API Manager 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Renuka Fernando]

Hi all,

Tested following in APICTL 3.2.0 - RC2

   1.

   Install API Operator
   -

  Interactive mode
  -

  Batch mode
  -

  With -f 
  -

  DockerHub registry type
  -

  HTTP registry type
  2.

   Uninstall API Operator
   3.

   Add an API in K8s cluster
   4.

   Update an existing API in K8s cluster
   5.

   Add/remove environment
   6.

   Initialize API
   7.

   Delete API in K8s cluster with given name and with from-file flag.
   8.

   Basic kubectl commands


Tested these scenarios in macOs Catalina (version 10.15.6), kubectl version
v1.17.3

No blockers found.

[+ Stable]

+1 to proceed with the release.


Thanks,

Renuka

On Fri, Aug 14, 2020 at 12:49 PM Chamindu Udakara  wrote:

> Hi all,
>
> I have tested the following in APICTL 3.2.0 - RC2.
>
>
>-
>
>Manage Environments (add/remove/list environments) and log in using
>email as the username.
>-
>
>List APIs/Applications using a super tenant/tenant users and as DevOps
>User.
>-
>
>Initialize an API without any flag, with the definition.yaml and using
>from OpenAPI/Swagger Specification
>-
>
>Set commands (Change export-directory)
>-
>
>Import API (as Admin and Devops user, using a secondary user store as
>well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS with
>documentations and thumbnails)
>-
>
>Import API-Products (as Admin and Devops user, using a secondary user
>store as well, Cross tenants import and with different combinations of
>optional flags)
>-
>
>Update an existing API by importing it again  with different endpoint
>configs for prod and dev environments (with --update flag)
>-
>
>Update the documentation and thumbnails of APIs  by importing it
>again  (with --update flag)
>-
>
>Export API (as Admin and Devops user, and across tenants, using a
>secondary user store as well, export GraphQL APIs,  SOAP service as a REST
>APIs and APIs with documentation and thumbnails)
>-
>
>Change the lifecycle status of an API deployed in APIM via APICTL.
>(using a secondary store as well)
>-
>
>Delete API-products, Apis, Apps (as Admin and Devops user, and using a
>secondary store)
>-
>
>Import API-Products (as Admin and Devops user, using a secondary user
>store as well,)
>-
>
>Exporting all APIs of a tenant (with export-apis command)
>-
>
>Export App (as DevOps/admin users, for super tenant/ tenant users also
>with subscriptions and keys)
>-
>
>Import App (as a directory and zip, and using a secondary user store)
>-
>
>Generating Keys (as DevOps/admin super tenant users, devop/admin
>tenant users, using a secondary user store as well for APIs and API
>products)
>-
>
>Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP endpoints
>with load-balanced and failover mechanisms, Dynamic endpoints, and AWS
>Lambda endpoints)
>
>
> Tested these scenarios in the Linux environment (Ubuntu 20.04) and Windows
> Environment (Windows10 -64Bit- 2005)
>
> No blockers found.
>
> [+ Stable]
>
> +1 to proceed with the release.
>
>
>
> On Thu, Aug 13, 2020 at 11:35 PM Naduni Pamudika  wrote:
>
>> Hi All,
>>
>> WSO2 Api Manager team is pleased to announce the second release candidate
>> of WSO2 API Manager Tooling 3.2.0 version.
>>
>> The WSO2 API Manager tooling provides the capability to import and export
>> APIs, Applications and API Products across multiple environments
>> seamlessly. Hence it provides greater flexibility to create CI/CD pipelines
>> for APIs, Applications and API Products.
>>
>> Apart from migrating APIs, Applications and API Products, it supports
>> Kubernetes API operator to deploy and manage APIs in the Kubernetes cluster
>> by reducing additional overheads for the DevOps.
>>
>> Please find the new features, improvements and fixes related to this
>> release in  the following links.
>> New Features
>> 
>> Fixed Issues
>> 
>>
>> Download the API Manager Tooling Distribution from here
>> .
>>
>> The tag to be voted upon is
>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.2.0-rc2
>>
>> Documentation:
>> https://apim.docs.wso2.com/en/next/learn/api-controller/getting-started-with-wso2-api-controller/
>>
>> Please download, test the tool and vote.
>>
>>
>> *[+] Stable - Go ahead and release*
>>
>> *[-] Broken - Do not release *(explain why)
>>
>>
>>
>> Best Regards,
>> WSO2 API Manager Team
>>
>> --
>> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc.
>> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com
>> [image: http://wso2.com/signature] 

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

[Chamindu Udakara]

Hi all,

I have tested the following in APICTL 3.2.0 - RC2.


   -

   Manage Environments (add/remove/list environments) and log in using
   email as the username.
   -

   List APIs/Applications using a super tenant/tenant users and as DevOps
   User.
   -

   Initialize an API without any flag, with the definition.yaml and using
   from OpenAPI/Swagger Specification
   -

   Set commands (Change export-directory)
   -

   Import API (as Admin and Devops user, using a secondary user store as
   well, importing GraphQL APIs,  SOAP service as a REST APIs and APIS with
   documentations and thumbnails)
   -

   Import API-Products (as Admin and Devops user, using a secondary user
   store as well, Cross tenants import and with different combinations of
   optional flags)
   -

   Update an existing API by importing it again  with different endpoint
   configs for prod and dev environments (with --update flag)
   -

   Update the documentation and thumbnails of APIs  by importing it again
   (with --update flag)
   -

   Export API (as Admin and Devops user, and across tenants, using a
   secondary user store as well, export GraphQL APIs,  SOAP service as a REST
   APIs and APIs with documentation and thumbnails)
   -

   Change the lifecycle status of an API deployed in APIM via APICTL.
   (using a secondary store as well)
   -

   Delete API-products, Apis, Apps (as Admin and Devops user, and using a
   secondary store)
   -

   Import API-Products (as Admin and Devops user, using a secondary user
   store as well,)
   -

   Exporting all APIs of a tenant (with export-apis command)
   -

   Export App (as DevOps/admin users, for super tenant/ tenant users also
   with subscriptions and keys)
   -

   Import App (as a directory and zip, and using a secondary user store)
   -

   Generating Keys (as DevOps/admin super tenant users, devop/admin tenant
   users, using a secondary user store as well for APIs and API products)
   -

   Multiple Endpoint Support in Windows (HTTP/REST, HTTP/SOAP endpoints
   with load-balanced and failover mechanisms, Dynamic endpoints, and AWS
   Lambda endpoints)


Tested these scenarios in the Linux environment (Ubuntu 20.04) and Windows
Environment (Windows10 -64Bit- 2005)

No blockers found.

[+ Stable]

+1 to proceed with the release.



On Thu, Aug 13, 2020 at 11:35 PM Naduni Pamudika  wrote:

> Hi All,
>
> WSO2 Api Manager team is pleased to announce the second release candidate
> of WSO2 API Manager Tooling 3.2.0 version.
>
> The WSO2 API Manager tooling provides the capability to import and export
> APIs, Applications and API Products across multiple environments
> seamlessly. Hence it provides greater flexibility to create CI/CD pipelines
> for APIs, Applications and API Products.
>
> Apart from migrating APIs, Applications and API Products, it supports
> Kubernetes API operator to deploy and manage APIs in the Kubernetes cluster
> by reducing additional overheads for the DevOps.
>
> Please find the new features, improvements and fixes related to this
> release in  the following links.
> New Features
> 
> Fixed Issues
> 
>
> Download the API Manager Tooling Distribution from here
> .
>
> The tag to be voted upon is
> https://github.com/wso2/product-apim-tooling/releases/tag/v3.2.0-rc2
>
> Documentation:
> https://apim.docs.wso2.com/en/next/learn/api-controller/getting-started-with-wso2-api-controller/
>
> Please download, test the tool and vote.
>
>
> *[+] Stable - Go ahead and release*
>
> *[-] Broken - Do not release *(explain why)
>
>
>
> Best Regards,
> WSO2 API Manager Team
>
> --
> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc.
> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com
> [image: http://wso2.com/signature] 
>
>

-- 
*Chamindu Udakara* | Software Engineer | WSO2 Inc
*mobile *: *+94 755285531 *| *email *: chami...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev