46 lines
1.2 KiB
Plaintext
46 lines
1.2 KiB
Plaintext
emqx_ee_bridge_redis {
|
|
|
|
command_template.desc:
|
|
"""Redis command template used to export messages. Each list element stands for a command name or its argument.
|
|
For example, to push payloads in a Redis list by key `msgs`, the elements should be the following:
|
|
`rpush`, `msgs`, `${payload}`."""
|
|
|
|
command_template.label:
|
|
"""Redis Command Template"""
|
|
|
|
config_enable.desc:
|
|
"""Enable or disable this bridge"""
|
|
|
|
config_enable.label:
|
|
"""Enable Or Disable Bridge"""
|
|
|
|
desc_config.desc:
|
|
"""Configuration for a Redis bridge."""
|
|
|
|
desc_config.label:
|
|
"""Redis Bridge Configuration"""
|
|
|
|
desc_name.desc:
|
|
"""Bridge name, used as a human-readable description of the bridge."""
|
|
|
|
desc_name.label:
|
|
"""Bridge Name"""
|
|
|
|
desc_type.desc:
|
|
"""The Bridge Type"""
|
|
|
|
desc_type.label:
|
|
"""Bridge Type"""
|
|
|
|
local_topic.desc:
|
|
"""The MQTT topic filter to be forwarded to Redis. All MQTT 'PUBLISH' messages with the topic
|
|
matching the local_topic will be forwarded.</br>
|
|
NOTE: if this bridge is used as the action of a rule (EMQX rule engine), and also local_topic is
|
|
configured, then both the data got from the rule and the MQTT messages that match local_topic
|
|
will be forwarded."""
|
|
|
|
local_topic.label:
|
|
"""Local Topic"""
|
|
|
|
}
|