From ad53523e6b98df0b6bc2fc8d39bfa56c82c20d5a Mon Sep 17 00:00:00 2001
From: "Zaiming (Stone) Shi" <zmstone@gmail.com>
Date: Mon, 19 Feb 2024 14:36:12 +0100
Subject: [PATCH] refactor: delete non-prod code

So far the retainer backend type is always `built_in_database`.
The slightly over-engineered pre-implementation to support
another backend is likely not going to fly as the EMQX
resource frame work is mostly for auth and data integration.
i.e. not generic enough for retained messages.
---
 apps/emqx_retainer/src/emqx_retainer.erl | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/apps/emqx_retainer/src/emqx_retainer.erl b/apps/emqx_retainer/src/emqx_retainer.erl
index fbf5e8e24..15f74353c 100644
--- a/apps/emqx_retainer/src/emqx_retainer.erl
+++ b/apps/emqx_retainer/src/emqx_retainer.erl
@@ -425,17 +425,7 @@ get_backend_module() ->
 
 create_resource(Context, #{type := built_in_database} = Cfg) ->
     emqx_retainer_mnesia:create_resource(Cfg),
-    Context;
-create_resource(Context, #{type := DB} = Config) ->
-    ResourceID = erlang:iolist_to_binary([io_lib:format("~ts_~ts", [?APP, DB])]),
-    _ = emqx_resource:create(
-        ResourceID,
-        <<"emqx_retainer">>,
-        list_to_existing_atom(io_lib:format("~ts_~ts", [emqx_connector, DB])),
-        Config,
-        #{}
-    ),
-    Context#{resource_id => ResourceID}.
+    Context.
 
 -spec close_resource(context()) -> ok | {error, term()}.
 close_resource(#{resource_id := ResourceId}) ->