yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
emqx/apps/emqx_bridge
History
Thales Macedo Garitezi 3954b7bde2 fix(bridges): function clause when a non-ingress bridge coexists with an egress bridge 
This was not caught by our tests because we always test bridge types
in isolation.  So, if the config only contains ingress-only bridges,
the `on_message_publish` hook is never installed.

In a real system, if there are bridges of mixed types in the config,
the hook might be installed, and `emqx_bridge:get_matched_bridge_id`
would crash when iterating over the ingress bridges.
 		2023-03-16 13:43:01 -03:00
..
etc chore: change the enable_pipelining default value 2022-05-31 19:32:53 +08:00
i18n docs: fix bridge status report 2023-02-28 11:56:46 +01:00
include feat(buffer_worker): add expiration time to requests 2023-01-20 11:36:52 -03:00
src fix(bridges): function clause when a non-ingress bridge coexists with an egress bridge 2023-03-16 13:43:01 -03:00
test test: fix inter-suite flakiness 2023-03-16 13:43:01 -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 fix(bridge): use the same dry run prefix 2023-03-16 13:43:01 -03: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.