+
Skip to content

Releases: MAIF/otoroshi

v17.4.0

09 Jul 14:13
Compare
Choose a tag to compare

Otoroshi version 17.4.0

https://github.com/MAIF/otoroshi/milestone/119?closed=1
v17.3.2...v17.4.0
https://github.com/MAIF/otoroshi/releases/tag/v17.4.0

Added

Changed

Documentation

Contributors

v17.3.2

05 Jun 13:58
Compare
Choose a tag to compare

v17.3.1

04 Jun 15:04
Compare
Choose a tag to compare

Otoroshi version 17.3.1

https://github.com/MAIF/otoroshi/milestone/117?closed=1
v17.3.0...v17.3.1
https://github.com/MAIF/otoroshi/releases/tag/v17.3.1

Added

Fixed

  • Map, FlatMap and Filter workflow nodes does not work as expected (#2193 fixed by mathieuancelin)

Documentation

Contributors

v17.3.0

03 Jun 11:40
Compare
Choose a tag to compare

Otoroshi version 17.3.0

https://github.com/MAIF/otoroshi/milestone/116?closed=1
v17.2.0...v17.3.0
https://github.com/MAIF/otoroshi/releases/tag/v17.3.0

Added

Fixed

Contributors

v17.2.0

20 May 15:50
Compare
Choose a tag to compare

Otoroshi version 17.2.0

https://github.com/MAIF/otoroshi/milestone/115?closed=1
v17.1.1...v17.2.0
https://github.com/MAIF/otoroshi/releases/tag/v17.2.0

Added

Changed

Fixed

Contributors

v17.1.1

05 May 12:47
Compare
Choose a tag to compare

Otoroshi version 17.1.1

https://github.com/MAIF/otoroshi/milestone/114?closed=1
v17.1.0...v17.1.1
https://github.com/MAIF/otoroshi/releases/tag/v17.1.1

Fixed

  • ensure OpenAPI is always up to date when releasing otoroshi (#2152)

Contributors

v17.1.0

25 Apr 16:28
Compare
Choose a tag to compare

Otoroshi version 17.1.0

https://github.com/MAIF/otoroshi/milestone/113?closed=1
v17.0.0...v17.1.0
https://github.com/MAIF/otoroshi/releases/tag/v17.1.0

Added

  • Migrate from proxy-wasm to a vanilla configuration for integrating Coraza. (#2134)
  • New loadbalancing strategy: LeastConnections (#2142)
  • New loadbalancing strategy: Power Of Two Random Choices (#2143)
  • Add ServiceDescriptor migration logs for Kubernetes Ingress job (#2144)
  • Support Route in the Kubernetes Ingress job (#2145)
  • New canary mode plugin with autonomous rollout (#2146)
  • Coraza can inspect input / output bodies separately (#2151)

Changed

  • Remove http-wasm spec (#2140)
  • Remove proxy-wasm spec (#2141)

Fixed

  • CRDs import should warn user when importing ServiceDescriptors (#2130)
  • Coraza only understand unsigned bytes for body payloads (#2150)

Contributors

v17.0.0

31 Mar 15:03
Compare
Choose a tag to compare

Otoroshi version 17.0.0

https://github.com/MAIF/otoroshi/milestone/112?closed=1
v16.24.0...v17.0.0
https://github.com/MAIF/otoroshi/releases/tag/v17.0.0

⚠️ Breaking changes ⚠️

there was some internal API breaking changes in Otoroshi 17.0.0. So if you're building plugins, you might need to adapt your code

  • the type of otoroshi.plugins.Keys.ExtraAnalyticsDataKey is now JsObject instead of JsValue
  • the type of otoroshi.plugins.Keys.GatewayEventExtraInfosKey is now JsObject instead of JsValue
  • the type of otoroshi.next.plugins.Keys.PreExtractedApikeyKey is now Either[(Option[ApiKey], Option[String]), ApiKey] instead of Either[Option[ApiKey], ApiKey]
  • method def template(version: String, params: Map[String, String], ctx: Option[ApiActionContext[_]] = None): JsValue in otoroshi.api.ResourceAccessApi[T] now takes an additional ctx: Option[ApiActionContext[_]] = None param

New features

Otoroshi now introduces a new core entity: APIs. This feature marks a major step towards a more API Management–oriented experience by allowing users to manage their APIs as a whole, rather than configuring them route by route. With the API entity, you can define reusable backends, declare multiple plugin flows that can be applied across different paths, manage consumers and subscriptions, and track the state of an API throughout its lifecycle. This evolution unlocks powerful capabilities for building developer portals and brings Otoroshi closer to the expectations of a full-featured API Management platform.

APIs are now available is with alpha tag. The documentation and tutorial are coming in next versions. Do not hesitate to provide feedback to make it a killer feature

Sunsetting Service Descriptors

For more than 2 years, after the rewrite of the proxy engine in v1.5.3, Service Descriptors has been deprecated.

Now (v17.0.0) it’s time to go ahead and provide some migration tools to help users getting rid of Service Descriptor in favor of routes before completely removing support of Service Descriptors in v18.0.0 (probably in 2026). Under the hood the new proxy engine already convert your Service Descriptors to Route in order to route traffic to your backends. The idea here is to remove the Service Descriptor entity in favor of the Route entity and let the user adapt their workflows and automations.

You can read more about it here

Added

  • API entity with full lifecycle management (#2098)
  • Support flows of plugins (#2101)
  • Allow defining custom routes in API (#2102)
  • Allow defining custom backends in API (#2103)
  • Allow defining custom customers in API (#2104)
  • Allow defining custom subscriptions in API (#2105)
  • Expose full API health and metrics dashboard (#2106)
  • Implement API state management (#2107)
  • Investigate API deployment lifecycle management (#2108)
  • Allow activating circuit breaker on a specific route only (#2111)
  • Support target failover (#2113)
  • Allow Expression Language to use private apps user tokens (#2115)
  • Support JDK 24 (#2116)
  • allow to select a specific api group in the admin api openapi descriptor (#2118)
  • allow openapi to be consumed as yaml (#2119)
  • Add extra information in GatewayEvent about apikey rejection reason (#2120)
  • Add matched jwt verifier in GatewayEvents and attrs (#2124)
  • ServiceDescriptor migration toolkit (#2125)

Changed

  • Change the type of otoroshi.plugins.keys.ExtraAnalyticsData (#2126)
  • Change the type of otoroshi.plugins.keys.GatewayEventExtraInfos (#2127)

Fixed

  • Admin API should not be served in worker mode (#2112)
  • Scala schema fails on some SDK annotations (#2117)

Contributors

v16.24.0

26 Feb 08:45
Compare
Choose a tag to compare

Otoroshi version 16.24.0

https://github.com/MAIF/otoroshi/milestone/111?closed=1
v16.23.2...v16.24.0
https://github.com/MAIF/otoroshi/releases/tag/v16.24.0

Added

  • CORS plugin: Accept * as Access-Control-Allow-Headers (#2099)

Changed

  • enhance secret vaults doc (#2090)
  • No Route data in GatewayEvent logs when a call is blocked by Otoroshi (#2092)
  • Ensure correct tenant and teams are displayed when creating new entities (#2096)
  • Ensure the correct tenant and teams are displayed when using 'Get from OIDC config' (#2097)

Fixed

  • fix kubernetes vault implementation (#2091)
  • pulsar connector cannot use basic or token auth. (#2110)

Documentation

  • enhance secret vaults doc (#2090)

Contributors

v16.23.2

04 Feb 14:05
Compare
Choose a tag to compare

Otoroshi version 16.23.2

https://github.com/MAIF/otoroshi/milestone/109?closed=1
v16.23.1...v16.23.2
https://github.com/MAIF/otoroshi/releases/tag/v16.23.2

Added

  • add sidebar category for WAF (#2084)
  • upgrade coraza to use latest CRS (#2085)
  • Allow extensions to use CodeInput (#2088)

Changed

Fixed

  • recursive call in the privateapp session manager (#2086)

Contributors

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载