[Feature Request]: Make MQTT trigger more robust #3416

dberardo-com · 2024-12-04T10:35:52Z

Feature Type

Adding new functionality to Nuclio
Changing existing functionality in Nuclio
Removing existing functionality in Nuclio

Problem Description

I have already reported in the past that the current implementation of the mqtt trigger in nuclio makes it simply unusable in real-life environment due to the "clean_session: true" parameter, which causes the client to "forget" about all topics it was subscribed to in case of disconnection/reconnection from the broker.

Also, it makes no sense to allow the user to subscribe with QoS > 0 if clean_session: true and the clientId changes when the container is restarted.

Feature Description

Must:

remove clean session true
use a static clientId --> this could be a parameter from the trigger, or the name of the function with an identifier like the context_id
(if using mqtt v5) allow sessionTimeout and keepalive configuration

Nice to have

allow for websocket connection
allow for usage of certificates to authenticate

Alternative Solutions

unfortunately i am not able to use the mqtt trigger so far and need to manually connect from inside the function using an HTTP trigger instead ... quite annoying

Additional Context

No response

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Feature Request]: Make MQTT trigger more robust #3416

[Feature Request]: Make MQTT trigger more robust #3416

[Feature Request]: Make MQTT trigger more robust #3416

[Feature Request]: Make MQTT trigger more robust #3416

Comments

Feature Type

Problem Description

Feature Description

Alternative Solutions

Additional Context