Renuka Piyumal Fernando

### Description: Gateway type is auto switched to regular gateway from choreo-connect when a new version of an API is created. ### Steps to reproduce: 1. Create an API 2....

### Description: $subject ### Steps to reproduce: 1. Create an API 2. Go to policies and switched to choreo connect 3. Add policies 4. Save and deploy 5. Export API...

Support for month, year ratelimit units

1

*Title*: *Support for month, year ratelimit units* *Description*: Rate limits such as `10K req/Month`, `1M req/year` are useful when **the upstream has a business value** (like a per month ***subscription***)...

Enable setting `hits_addend` dynamically (from a request header value or dynamic metadata) will help to implement a global bandwidth rate limit solution.

Feature request: Stop incrementing cache keys when overall status is over limited

2

## Scenario Let's say we have grouped routes 1. Group: **Foo** 1. /foo/v1/hello-1 2. Group: **Bar** 1. /bar/v1/hello-1 2. /bar/v1/hello-special And we need to apply the following rate limits. 1....

### Description: $subject This can be used for Istio scenarios, where direct service-to-service communication in Istio scenario (without virtual services and gateways)

### Describe your problem(s) logs with request/response body when it is enabled. ### Describe your solution Add descriptive debug and trace logs. https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-component-log-level ### How will you implement it ---...

### Describe your problem(s) $subject Config TOML ```toml [adapter.consul] enabled = true url = "http://consul-server.consul:8500" pollInterval = 5 ACLToken = "" mgwServiceName = "choreo-connect" serviceMeshEnabled = true caCertFile = "/home/wso2/security/truststore/consul/consul-agent-ca.pem"...

### Describe your problem(s) Unable to provide a context path in endpoints with consul service discovery. For example, the adapter does not accept the following endpoint with base path `/train-operations/v1...

### Describe your problem(s) Currently, we are keeping JWTValidator per API (per auth filter) https://github.com/wso2/product-microgateway/blob/e696247296e1bc7a92ba50b042081631a4700500/enforcer-parent/enforcer/src/main/java/org/wso2/choreo/connect/enforcer/security/jwt/JWTAuthenticator.java#L77 It should be per Key manager https://github.com/wso2/product-microgateway/blob/51303937f8b421660770bc244d87f82ab1951668/enforcer-parent/enforcer/src/main/java/org/wso2/choreo/connect/enforcer/keymgt/KeyManagerHolder.java#L76 ### Describe your solution ### How will you...