benthosdev/benthos v4.27.0 on GitHub

For installation instructions check out the getting started guide.

New nats_kv cache type.
The nats_jetstream input now supports last_per_subject and new deliver fallbacks.
Field error_patterns added to the drop_on output.
New redis_scan input type.
Field auto_replay_nacks added to all inputs that traditionally automatically retry nacked messages as a toggle for this behaviour.
New retry processor.
New noop cache.
Field targets_input added to the azure_blob_storage input.
New reject_errored output.
New nats_request_reply processor.
New json_documents scanner.

The unarchive processor no longer yields linting errors when the format csv:x is specified. This is a regression introduced in v4.25.0.
The sftp input will no longer consume files when the watcher cache returns an error. Instead, it will reattempt the file upon the next poll.
The aws_sqs input no longer logs error level logs for visibility timeout refreshing errors.
The nats_kv processor now allows nats wildcards for the keys operation.
The nats_kv processor keys operation now returns a single message with an array of found keys instead of a batch of messages.
The nats_kv processor history operation now returns a single message with an array of objects containing the record fields instead of a batch of messages.
Field timeout added to the nats_kv processor to specify the maximum period to wait on an operation before aborting and returning an error.
Bloblang comparison operators (>, <, <=, >=) now match the precision of the compared integers when applicable.
The parse_form_url_encoded Bloblang method no longer produces results with an unknown data type for repeated query parameters.
The echo CLI command no longer fails to sanitise configs when encountering an empty password field.

The log events from all inputs and outputs when they first connect have been made more consistent and no longer contain any information regarding the nature of their connections.
Splitting message batches with a split processor (or custom plugins) no longer results in downstream error handling loops around nacks. This was previously implemented as a feature to ensure unbounded expanded and split batches don't flood downstream services in the event of a minority of errors. However, introducing more clever origin tracking of errored messages has eliminated the need for this undocumented behaviour.

The full change log can be found here.