This allows a n:1 relation between v1 bridge_types to action/connector types as it's the case with mongodb for instance, where we had `mongodb_single` `mongodb_sharded` etc and the new implementation will just have `mongodb`. |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| src | ||
| test | ||
| .gitignore | ||
| README.md | ||
| rebar.config | ||
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.