Hi All,
Thanks for testing WSO2 API Manager Tooling v3.1.0-RC4.
Since the vote has been passed with 13 +1s and 0 -1s, we are hereby closing
the vote and proceeding with WSO2 API Manager Tooling v3.1.0 GA release.
Thanks,
WSO2 API Manager Team
On Mon, Apr 6, 2020 at 11:28 AM Hiranya Abeyrathne
Tested the following:
- Add/ list environment
- create API
- Publish API to WSO2 API Manager.
No blockers found.
*[+] Stable - Go ahead and release*
On Mon, Apr 6, 2020 at 9:01 AM Rajith Roshan wrote:
> Hi all,
> Tested the basic scenarios with microgateway.
>
> No blockers found
>
> *[+]
Hi all
Tested apictl with followings.
1. Install k8s api-operator and wso2am-operator in a k8s cluster
2. Tested API Operator scenarios with the apictl
3. Added environments and import the APIs
4. Generated keys for the imported APIs
5. Uninstall the API Operator using apictl
No
Hi,
Tested the apictl for the basic use cases of K8s API Operator. No blockers
found.
[+] Stable - Go ahead and release
Thank you!
On Sat, Apr 4, 2020 at 9:36 AM Renuka Fernando wrote:
> Hi all
>
> Tested apictl with followings.
>
>1. Install k8s api-operator in a k8s cluster
> -
Hi all
Tested apictl with followings.
1. Install k8s api-operator in a k8s cluster
- Batch mode (non interactive) with registry types: HTTP private
registry, DockerHub
- Interactive mode with registry types: GCR, AWS ECR
2. Install k8s wso2am-operator
3. Add a new API
Hi all,
I have tested the following.
- Manage Environments (add/remove/list environments) and log in using
email instead of username
- List APIs/Applications using a super tenant/tenant users
- Initialize an API without any flag, with the definition.yaml and using
from
