chore: improve the changes for configuration

This commit is contained in:
JianBo He 2023-04-18 15:50:08 +08:00 committed by 某文
parent 22a1d05d7b
commit e3a84e0010
2 changed files with 11 additions and 10 deletions

View File

@ -0,0 +1,7 @@
Hide a large number of advanced options to simplify the configuration file.
That includes `exhook`, `rewrite`, `topic_metric`, `persistent_session_store`, `overload_protection`,
`flapping_detect`, `conn_congestion`, `stats,auto_subscribe`, `broker_perf`, `rule_engine`, `bridge`,
`shared_subscription_group`, `slow_subs`, `ssl_options.user_lookup_fun` and some advance items
in `node` and `dashboard` section, [#10358](https://github.com/emqx/emqx/pull/10358),
[#10381](https://github.com/emqx/emqx/pull/10381), [#10385](https://github.com/emqx/emqx/pull/10385).

View File

@ -1,10 +1,4 @@
1. Changes in configuration priority:
For new EMQX installations, configuration priority is `ENV > emqx.conf > HTTP API`.
For upgrades from an older version with cluster-override.conf, configuration priority remains the same: `HTTP API > ENV > emqx.conf`.
2. Deprecation of `data/configs/local-override.conf`.
3. Simplified configuration items, hidden some advanced items
The hidden configurations include: exhook,rewrite,topic_metric,persistent_session_store,overload_protection,
flapping_detect,conn_congestion,stats,auto_subscribe,broker_perf,rule_engine,bridge,shared_subscription_group,slow_subs
ssl_options.user_lookup_fun and some advance items in node/dashboard.
4. This hidden update doesn't change the functionality of the original configuration,
but it sets the stage for an improved presentation of configuration documentation in future versions.
Optimize the configuration priority mechanism to fix the issue where the configuration
changes made to `etc/emqx.conf` do not take effect after restarting EMQX.
More introduction about the new mechanism: [Configure Override Rules](https://www.emqx.io/docs/en/v5.0/configuration/configuration.html#configure-override-rules)