|
|
%!s(int64=3) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| include | 583624fb8d fix(emqx_authn): fix test suite | %!s(int64=3) %!d(string=hai) anos |
| src | 1d023b541f refactor(connnector): rename waiting_connect_complete -> wait_for_resource_ready | %!s(int64=3) %!d(string=hai) anos |
| test | db0e9e3358 fix(emqx_resource_instance): fix dialyzer warning | %!s(int64=3) %!d(string=hai) anos |
| README.md | 071c2c99e8 refactor(authn resources): add `emqx_resource` and `emqx_authn` tests | %!s(int64=4) %!d(string=hai) anos |
| rebar.config | 542c9a2b68 refactor(emqx_resource): Decorate RPCs | %!s(int64=4) %!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_test_resource.erl for a minimal emqx_resource implementation;test/emqx_resource_SUITE.erl for examples of emqx_resource usage.