Distributed setup: select which parts of ~/local/ folder to synchronize
In distributed setups one usually selects to synchronize "MKP and local files" to remote sites.
The generic behavior resulting from this can lead to problems, e.g.:
* size of synchronization, e.g. when one has parts of local structure in version control systems (git, svn, etc.)
* should python modules have been added by executing "pip3 install [MODULENAME]" at central site, it's not unusual parts of the module get compiled. This could lead to problems should you have your sites running at different Linux-OSs or -versions.
I suggest to provide the option to select which parts of the ~/local/ folder to synchronize to a remote site, e.g.:
* MKPs and other files in standard CMK folders (like ~/local/share/check_mk/, ~/local/lib/python3/cmk/, etc.)
* automatically exclude all subfolders named ".git" or ".svn", have the option to explicitely enable them
* automatically exclude ~/local/lib/python2/ in CMK 2.X
* files in other folders than "cmk" in ~/local/lib/python3/
* something else ;-)
Comments: 1
-
15 Jul, '22
MarkusIt might also be helpful to ease distributed administration
* servers and rules may then be added on a remote site only. In a half controlled setup with sync of "~/local" enabled added servers AND rules will be overwritten (AFAIK)
* currently it is just possible not to have any sync at all or some homemade unsuported stuff
To resume I would like to have a complete sync BUT exclude ~/etc/check_mk/conf.d/wato