|
|
%!s(int64=2) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| include | 54c542c795 chore: rename _probe_ to t_probe_ | %!s(int64=2) %!d(string=hai) anos |
| src | 9143d5994d feat: refactor MS SQL Server bridge to connector and action | %!s(int64=2) %!d(string=hai) anos |
| test | 15f919e60f Merge pull request #12564 from thalesmg/bw-support-batch-list-resp-m-20240221 | %!s(int64=2) %!d(string=hai) anos |
| README.md | a2afdeeb48 feat: add test cases for batching query | %!s(int64=3) %!d(string=hai) anos |
| rebar.config | 8a0ca38a77 fix: drop no longer supported dialyzer option | %!s(int64=3) %!d(string=hai) anos |
The emqx_resource is a behavior that manages configuration specs and runtime states
for resources like mysql or redis backends.
It is intended to be used by the emqx_bridges and all other resources that need CRUD operations to their configs, and need to initialize the states when creating.
There can be foreign references between resource instances via resource-id. So they may find each other via this Id.
The main idea of the emqx resource is to put all the general code in a common lib, including
the config operations (like config validation, config dump back to files), and the state management.
And we put all the specific codes to the callback modules.
See
test/emqx_connector_demo.erl for a minimal emqx_resource implementation;test/emqx_resource_SUITE.erl for examples of emqx_resource usage.