|
|
3 lat temu | |
|---|---|---|
| .. | ||
| i18n | 9e50866cd0 fix: rename queue_max_bytes -> max_queue_bytes | 3 lat temu |
| include | 0ef0b68de4 refactor: change '{recoverable_error,Reason}' to '{error,{recoverable_error,Reason}}' | 3 lat temu |
| src | 26234d38b9 fix: mark the async msg 'queuing' not 'sent.inflight' on recoverable_error | 3 lat temu |
| test | 26234d38b9 fix: mark the async msg 'queuing' not 'sent.inflight' on recoverable_error | 3 lat temu |
| README.md | a2afdeeb48 feat: add test cases for batching query | 3 lat temu |
| rebar.config | 02c3f87b31 style: reformat all remaining apps | 3 lat temu |
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.