History

Thales Macedo Garitezi 676df7eb30 test(gcp_pubsub_consumer): add test case for updating topic when there is a topic mapping Checks that, if a migrated bridge originally has a `topic_mapping` and is later updated with V2 APIs (without topic mapping in the input), then the new V2 `topic` field prevails.		2024-03-05 09:12:24 -03:00
..
etc	chore: change the enable_pipelining default value	2022-05-31 19:32:53 +08:00
include	chore: update copyright-year	2024-02-23 08:21:06 +01:00
src	Merge pull request #12595 from thalesmg/kafka-consumer-source-m-20240223	2024-03-01 10:11:16 +08:00
test	test(gcp_pubsub_consumer): add test case for updating topic when there is a topic mapping	2024-03-05 09:12:24 -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: erlfmt all `rebar.config` files and `bin/nodetool`	2023-12-29 09:08:03 +08: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.