From 46c9fb0220aeaa289b28121104df2e6c7d8de8c6 Mon Sep 17 00:00:00 2001 From: zed Date: Tue, 31 Jan 2023 17:40:07 +0300 Subject: [PATCH] document lexicographic order for config.d/ files --- docs/features/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/README.md b/docs/features/README.md index 25c2761d8..b8fe7c6cd 100644 --- a/docs/features/README.md +++ b/docs/features/README.md @@ -916,7 +916,7 @@ Starting from Imunify360 v.5.8, we introduce the overridable config which provid **Configs organization**: * A new directory for custom configs. The local overrides of Imunify360 config are put there: `/etc/sysconfig/imunify360/imunify360.config.d/` -* The old config `/etc/sysconfig/imunify360/imunify360.config` is now linked to the `imunify360.config.d/90-local.config`. It contains changes made through UI as well as through CLI. +* The old config `/etc/sysconfig/imunify360/imunify360.config` is now linked to the `imunify360.config.d/90-local.config`. It contains changes made through UI as well as through CLI. Custom config files are loaded in a lexicographical order e.g., `10_on_first_install.config` is loaded before `90-local.config` and therefore UI/CLI config updates override values from `10_on_first_install.config`, and correspondingly values put into `99-highest-priority.config` won't be overriden by UI/CLI. Note: `100-likely-an-error.config` is loaded *before* `90-local.config` (according to the lexicographical order). * Default Imunify360 configuration is written at `imunify360.config.defaults.example`. Modifying this config won't affect config merging behavior in any way, so please refrain from changing it. * Configs in that directory will override the `imunify360.config.defaults.example` and each other in lexical order. First-level "sections" (such as `FIREWALL`) are merged, while second-level "options" (such as `FIREWALL.TCP_IN_IPv4`) are replaced completely. * `imunify360.config.d/10_on_first_install.config` is a config that is supplied by Imunify360. Its purpose is to let us - Imunify360 developers - enable new features only on new installations without forcing existing installation to see new feature enabled on the update. This config should not be modified manually.