fix: add `emqx_s3` to `reboot_lists.eterm`
Otherwise, it's unconditionally started as a permanent application instead of being controlled by `emqx_machine`. ```sh ͳ rg start_boot _build/emqx-enterprise/rel/emqx/releases/5.7.0-g4e6be8a6/start.script | rg emqx_s3 {apply,{application,start_boot,[emqx_s3,permanent]}}, ```
This commit is contained in:
parent
945ea785ae
commit
198ccd320b
|
@ -117,6 +117,7 @@
|
||||||
emqx_bridge_oracle,
|
emqx_bridge_oracle,
|
||||||
emqx_bridge_rabbitmq,
|
emqx_bridge_rabbitmq,
|
||||||
emqx_bridge_azure_event_hub,
|
emqx_bridge_azure_event_hub,
|
||||||
|
emqx_s3,
|
||||||
emqx_bridge_s3,
|
emqx_bridge_s3,
|
||||||
emqx_schema_registry,
|
emqx_schema_registry,
|
||||||
emqx_eviction_agent,
|
emqx_eviction_agent,
|
||||||
|
|
Loading…
Reference in New Issue