< Back to all releases

v0.44.18

Enables FSMv2 communicator by default.

Improvements

  • The FSMv2 communicator is now enabled by default. Previously, enterprise networks with firewalls that dropped idle connections could leave instances appearing offline in the Management Console until the container was restarted. The new communicator uses separate connections for status and commands, so a dropped pull connection no longer prevents heartbeats from reaching the backend, and it recovers automatically when the connection comes back. The memory cleanup routine it depends on is also enabled by default. If you previously disabled FSMv2 by setting useFSMv2Transport: false in config.yaml, that setting has had no effect since v0.44.8 -- to keep the legacy communicator you must set USE_FSMV2_TRANSPORT=false as an environment variable. To roll back, set USE_FSMV2_TRANSPORT=false and USE_FSMV2_MEMORY_CLEANUP=false.

Preview: Write Flows

  • Previously, write flows used raw input for benthos. We now define a user variable UMH_TOPICS and automatically generate the proper input in umh-core, which provides an improved user experience and less surface for errors.
Discuss on Discord