diff --git a/README.md b/README.md index 9cbea2c35c..43607b21a5 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ [![Build Status](https://wso2.org/jenkins/job/products/job/product-microgateway/badge/icon)](https://wso2.org/jenkins/job/products/job/product-microgateway/) [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0) -[![License](https://img.shields.io/badge/slack-microgateway-blueviolet)](https://join.slack.com/t/wso2-apim/shared_invite/enQtNzEzMzk5Njc5MzM0LTgwODI3NmQ1MjI0ZDQyMGNmZGI4ZjdkZmI1ZWZmMjNkY2E0NmY3ZmExYjkxYThjNzNkOTU2NWJmYzM4YzZiOWU) +[![Discord](https://img.shields.io/badge/Discord-7289DA?logo=discord&logoColor=white)](https://discord.com/invite/Xa5VubmThw) Choreo Connect is a cloud-native, open-source, and developer-centric API gateway proxy. It provides first-class support for K8s while facilitating an array of API management quality of services (QoS), such as message security rate-limiting, observability, and message mediation. @@ -31,7 +31,7 @@ Let's host our first API on Choreo Connect. We will be exposing the publicly ava 1. First download the latest CLI tool(APICTL) and the Choreo Connect distributions and extract them to a folder of your choice. - * [CLI (APICTL - v4.1.x)](https://github.com/wso2/product-apim-tooling/releases/) + * [CLI (APICTL - v4.2.x)](https://github.com/wso2/product-apim-tooling/releases/) * [Choreo Connect Distribution](https://github.com/wso2/product-microgateway/releases/) CLI tool extracted location will be referred as `CLI_HOME` and Choreo Connect distribution extracted location would be referred as `CC_HOME`. diff --git a/dev-scripts/remove-containers.sh b/dev-scripts/remove-containers.sh index 9df2011b84..bd59a6d559 100644 --- a/dev-scripts/remove-containers.sh +++ b/dev-scripts/remove-containers.sh @@ -16,7 +16,7 @@ # ----------------------------------------------------------------------- # Just to assist developers by removing all the containers. -cc_version=1.2.0-beta +cc_version=1.2.0 docker kill "$(docker ps -a | grep wso2/choreo-connect-enforcer:$cc_version | awk '{print $1}')" docker rm "$(docker ps -a | grep wso2/choreo-connect-enforcer:$cc_version | awk '{print $1}')" diff --git a/integration/test-integration/src/test/resources/dockerCompose/cc-cacert-mounted-mtls.yaml b/integration/test-integration/src/test/resources/dockerCompose/cc-cacert-mounted-mtls.yaml index 0476b926ec..c2f6b215ca 100644 --- a/integration/test-integration/src/test/resources/dockerCompose/cc-cacert-mounted-mtls.yaml +++ b/integration/test-integration/src/test/resources/dockerCompose/cc-cacert-mounted-mtls.yaml @@ -1,7 +1,7 @@ version: "3.7" services: router: - image: wso2/choreo-connect-router:1.2.0-beta + image: wso2/choreo-connect-router:1.2.0 logging: options: max-size: "20m" @@ -32,7 +32,7 @@ services: - adapter - enforcer adapter: - image: wso2/choreo-connect-adapter:1.2.0-beta + image: wso2/choreo-connect-adapter:1.2.0 logging: options: max-size: "20m" @@ -51,7 +51,7 @@ services: - "18000:18000" - "9843:9843" enforcer: - image: wso2/choreo-connect-enforcer:1.2.0-beta + image: wso2/choreo-connect-enforcer:1.2.0 logging: options: max-size: "20m" diff --git a/integration/test-integration/src/test/resources/dockerCompose/cc-in-common-network-docker-compose.yaml b/integration/test-integration/src/test/resources/dockerCompose/cc-in-common-network-docker-compose.yaml index 018b98ac0d..687908b1f8 100644 --- a/integration/test-integration/src/test/resources/dockerCompose/cc-in-common-network-docker-compose.yaml +++ b/integration/test-integration/src/test/resources/dockerCompose/cc-in-common-network-docker-compose.yaml @@ -7,7 +7,7 @@ networks: name: apim_and_cc services: router: - image: wso2/choreo-connect-router:1.2.0-beta + image: wso2/choreo-connect-router:1.2.0 logging: options: max-size: "20m" @@ -35,7 +35,7 @@ services: networks: - cc_internal adapter: - image: wso2/choreo-connect-adapter:1.2.0-beta + image: wso2/choreo-connect-adapter:1.2.0 logging: options: max-size: "20m" @@ -58,7 +58,7 @@ services: - cc_internal - apim_and_cc enforcer: - image: wso2/choreo-connect-enforcer:1.2.0-beta + image: wso2/choreo-connect-enforcer:1.2.0 logging: options: max-size: "20m" diff --git a/release-note.html b/release-note.html index 86df88fb0b..9f7ad073b8 100644 --- a/release-note.html +++ b/release-note.html @@ -17,83 +17,89 @@ ~ under the License. --> - + + - - Choreo Connect 1.1.0 - 3rd April 2022 + + Choreo Connect 1.2.0 - 11th March 2023 + -
-
-

Choreo Connect 1.1.0 is Released.

-

Choreo Connect is a cloud-native, open-source, and developer-centric API gateway. It provides first-class support for - Kubernetes while facilitating an array of API management quality of services (QoS), such as message - security rate-limiting, observability, and message mediation. It is powered by Envoy Proxy!

-

Choreo Connect 1.1.0 is also compatible with WSO2 API Manager 4.1.0.

-

What's new in 1.1.0

-

New Features

- -

- More - about 1.1.0 New Features

-

Improvements

- -

- More - about 1.1.0 Improvements

-

Bug fixes

-

- Bug - fixes

-

Known Issues

-

Open - Issues

-

Try it

-

- Quick start guide

-

How To Contribute

-

Your feedback is most welcome!

-

Contributing Code

-

Read through the project Contribution - Guidelines to learn how to contribute with code.

-

User Forum

-

If you have any questions regarding the product you can use our StackOverflow forum to - raise them.

-

Slack Channels

-

Join us via this to our wso2-apim.slack.com for even better communication. - You can talk to our developers directly regarding any issues, concerns about the product. We encourage you - to start discussions or join any ongoing discussions with the team, via our slack channels.

-

Reporting Issues

-

We encourage you to report issues, documentation faults, and feature requests regarding Choreo Connect - through the Github Issues.

-

And please be advised that security issues must be reported to security@wso2.com, - not as a GitHub issue, in order to reach the proper audience. We strongly advise following the +

+

Choreo Connect 1.2.0 is Released.

+

Choreo Connect is a cloud-native, open-source, and developer-centric API gateway. It provides first-class + support for + Kubernetes while facilitating an array of API management quality of services (QoS), such as message + security rate-limiting, observability, and message mediation. It is powered by Envoy Proxy!

+

Choreo Connect 1.2.0 is also compatible with WSO2 API Manager 4.2.0.

+

What's new in 1.2.0

+

New Features

+
    +
  • GraphQL API support
  • +
  • HTTP2 support
  • +
  • SOAP APIs support
  • +
  • Open Telemetry support
  • +
  • Mutual SSL authentication for APIs
  • +
  • Support Operation Level API Policies
  • +
  • JWKS Endpoint for the Enforcer
  • +
  • Compression Filter for Choreo Connect
  • +
+

+ More + about 1.2.0 New Features +

+

Improvements and Bug Fixes

+

+ Improvements +

+

+ Bug + fixes +

+

Known Issues

+

Open + Issues

+

Try it

+

+ Quick start guide +

+

How To Contribute

+

Your feedback is most welcome!

+

Contributing Code

+

Read through the project Contribution + Guidelines to learn how to contribute with code.

+

User Forum

+

If you have any questions regarding the product you can use our StackOverflow forum to + raise them.

+

Slack Channels

+

Join us via this to our WSO2 Discord account for even better communication. You can talk to + our developers directly + regarding any issues, concerns about the product. We encourage you to start discussions or join any + ongoing + discussions with the team, via Discord.

+

Reporting Issues

+

We encourage you to report issues, documentation faults, and feature requests regarding Choreo Connect + through the Github Issues.

+

And please be advised that security issues must be reported to security@wso2.com, + not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security - issues.

-

--Choreo Connect Team--

-
+ issues.

+

--Choreo Connect Team--

+
+ - + + \ No newline at end of file diff --git a/resources/docker-compose/apim/docker-compose.yaml b/resources/docker-compose/apim/docker-compose.yaml index d3967c4d46..84640b7c4d 100644 --- a/resources/docker-compose/apim/docker-compose.yaml +++ b/resources/docker-compose/apim/docker-compose.yaml @@ -14,7 +14,7 @@ services: volumes: - ./conf/deployment.toml:/home/wso2carbon/wso2-config-volume/repository/conf/deployment.toml router: - image: wso2/choreo-connect-router:1.2.0-beta + image: wso2/choreo-connect-router:1.2.0 logging: options: max-size: "20m" @@ -43,7 +43,7 @@ services: - adapter - enforcer adapter: - image: wso2/choreo-connect-adapter:1.2.0-beta + image: wso2/choreo-connect-adapter:1.2.0 logging: options: max-size: "20m" @@ -63,7 +63,7 @@ services: links: - apim enforcer: - image: wso2/choreo-connect-enforcer:1.2.0-beta + image: wso2/choreo-connect-enforcer:1.2.0 logging: options: max-size: "20m" diff --git a/resources/docker-compose/docker-compose.yaml b/resources/docker-compose/docker-compose.yaml index abf11db6f2..ab56e6a45b 100644 --- a/resources/docker-compose/docker-compose.yaml +++ b/resources/docker-compose/docker-compose.yaml @@ -1,7 +1,7 @@ version: "3.7" services: router: - image: wso2/choreo-connect-router:1.2.0-beta + image: wso2/choreo-connect-router:1.2.0 logging: options: max-size: "20m" @@ -31,7 +31,7 @@ services: - adapter - enforcer adapter: - image: wso2/choreo-connect-adapter:1.2.0-beta + image: wso2/choreo-connect-adapter:1.2.0 logging: options: max-size: "20m" @@ -50,7 +50,7 @@ services: - "18000:18000" - "9843:9843" enforcer: - image: wso2/choreo-connect-enforcer:1.2.0-beta + image: wso2/choreo-connect-enforcer:1.2.0 logging: options: max-size: "20m" diff --git a/resources/k8s-artifacts/choreo-connect/adapter-deployment.yaml b/resources/k8s-artifacts/choreo-connect/adapter-deployment.yaml index a0f1777465..0591d1e03e 100644 --- a/resources/k8s-artifacts/choreo-connect/adapter-deployment.yaml +++ b/resources/k8s-artifacts/choreo-connect/adapter-deployment.yaml @@ -47,7 +47,7 @@ spec: - mountPath: /home/wso2/conf/log_config.toml subPath: log_config.toml name: logconfig-toml-vol - image: wso2/choreo-connect-adapter:1.2.0-beta + image: wso2/choreo-connect-adapter:1.2.0 imagePullPolicy: IfNotPresent env: - name: ADAPTER_PRIVATE_KEY_PATH diff --git a/resources/k8s-artifacts/choreo-connect/choreo-connect-deployment.yaml b/resources/k8s-artifacts/choreo-connect/choreo-connect-deployment.yaml index 6220b5b5e3..51101235ed 100644 --- a/resources/k8s-artifacts/choreo-connect/choreo-connect-deployment.yaml +++ b/resources/k8s-artifacts/choreo-connect/choreo-connect-deployment.yaml @@ -40,7 +40,7 @@ spec: - mountPath: /home/wso2/conf/log4j2.properties subPath: log4j2.properties name: log4j2-vol - image: wso2/choreo-connect-enforcer:1.2.0-beta + image: wso2/choreo-connect-enforcer:1.2.0 imagePullPolicy: IfNotPresent env: - name: ENFORCER_PRIVATE_KEY_PATH @@ -104,7 +104,7 @@ spec: name: router-keystore-vol - mountPath: /home/wso2/security/truststore name: router-truststore-vol - image: wso2/choreo-connect-router:1.2.0-beta + image: wso2/choreo-connect-router:1.2.0 imagePullPolicy: IfNotPresent env: - name: ROUTER_ADMIN_HOST