Zaiming Shi e6232665a3 refactor(emqx): ensure app shutdown and reboot order 4 роки тому
..
examples 704af9f3b1 The config handler phase2 (#5052) 4 роки тому
include 8978464269 change resource,connectors,data_bridges as normal apps (#5034) 4 роки тому
scripts 2a31c43e0d feat(emqx_resource): add behaviour emqx_resource 4 роки тому
src e6232665a3 refactor(emqx): ensure app shutdown and reboot order 4 роки тому
Makefile 2a31c43e0d feat(emqx_resource): add behaviour emqx_resource 4 роки тому
README.md fdd0233103 feat(emqx_resource): update the demo.md 4 роки тому
demo.sh 2a31c43e0d feat(emqx_resource): add behaviour emqx_resource 4 роки тому
elvis.config 2a31c43e0d feat(emqx_resource): add behaviour emqx_resource 4 роки тому
rebar.config 9617b65d52 fix(dialyzer): incorrect function spec 4 роки тому

README.md

emqx_resource

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_data_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.

Try it out

$ ./demo.sh
Eshell V11.1.8  (abort with ^G)
1> == the demo log tracer <<"log_tracer_clientid_shawn">> started.
config: #{<<"config">> =>
            #{<<"bulk">> => <<"10KB">>,<<"cache_log_dir">> => <<"/tmp">>,
                <<"condition">> => #{<<"clientid">> => <<"abc">>},
                <<"level">> => <<"debug">>},
        <<"id">> => <<"log_tracer_clientid_shawn">>,
        <<"resource_type">> => <<"log_tracer">>}
1> emqx_resource_instance:health_check(<<"log_tracer_clientid_shawn">>).
== the demo log tracer <<"log_tracer_clientid_shawn">> is working well
state: #{health_checked => 1,logger_handler_id => abc}
ok

2> emqx_resource_instance:health_check(<<"log_tracer_clientid_shawn">>).
== the demo log tracer <<"log_tracer_clientid_shawn">> is working well
state: #{health_checked => 2,logger_handler_id => abc}
ok

3> emqx_resource_instance:query(<<"log_tracer_clientid_shawn">>, get_log).
== the demo log tracer <<"log_tracer_clientid_shawn">> received request: get_log
state: #{health_checked => 2,logger_handler_id => abc}
"this is a demo log messages..."

4> emqx_resource_instance:remove(<<"log_tracer_clientid_shawn">>).
== the demo log tracer <<"log_tracer_clientid_shawn">> stopped.
state: #{health_checked => 0,logger_handler_id => abc}
ok

5> emqx_resource_instance:query(<<"log_tracer_clientid_shawn">>, get_log).
** exception error: {get_instance,{<<"log_tracer_clientid_shawn">>,not_found}}