End up client after a defined number of messages

[tardich]

Expected behavior

I'm using mqtt-cli to backup my zigbee2mqtt environment. In order to do so, I:

1. publish an empty message to this topic: zigbee2mqtt/bridge/request/backup
2. subscribe to zigbee2mqtt/bridge/response/backup

The content of this topic is the actual backup in json format

So the way I'm doing it is, from kubernetes, having a pod with two initContainers:

1. publish
2. subscribe

and the actual container which extracts the message received in the second initContainer, stored in a volume for that matter

In order for this container to run, the second initContainer must exit after it receives ONE message in the topic.

Actual behavior

The container (the initContainer in my case) waits indefinitely, which prevents the "extractor" to do its job.

To Reproduce

Steps

N/A

Reproducer code

N/A

Details

• Affected MQTT CLI version(s): hivemq/mqtt-cli:4.36.0
• Used JVM version: Irrelevant