emqx/apps/emqx_bridge
Thales Macedo Garitezi 35dc75b7ed feat(mqtt): add option to customize clientid prefix for egress bridges
https://emqx.atlassian.net/browse/EMQX-8445

Currently the bridge client’s client ID is prefixed with the resource
ID.

Sometimes it’s useful for users to have control of this prefix,
e.g. prefix based ACL rules in the target broker.
2022-12-23 09:50:26 -03:00
..
etc feat: generate a minimized emqx.conf 2022-05-31 19:20:27 +08:00
i18n Merge tag 'v5.0.10' into dev/ee5.0 2022-11-16 16:20:30 +01:00
include feat(bridge): add Redis bridge 2022-12-06 23:15:42 +03:00
src refactor: default mqtt bridgge buffer pool size down to 4 2022-12-19 23:59:46 +01:00
test feat(mqtt): add option to customize clientid prefix for egress bridges 2022-12-23 09:50:26 -03:00
.gitignore refactor(bridge): rename emqx_data_bridge to emqx_bridge 2021-09-10 11:43:03 +08:00
README.md docs(README): EMQ X -> EMQX 2022-02-15 16:19:26 +01:00
rebar.config style: reformat all remaining apps 2022-04-27 15:51:18 +02:00

README.md

emqx_bridge

EMQX Data Bridge is an application that managing the resources (see emqx_resource) used by emqx rule engine.

It provides CRUD HTTP APIs of the resources, and is also responsible for loading the resources at startup, and saving configs of resources to data/ after configs updated.

The application depends on emqx_connector as that's where all the callback modules of connector resources placed.