Werk #20236: Setup GIT integration: track MKP rule packs and configuration outside of the wato directories
| Component | Setup | ||||||
| Title | Setup GIT integration: track MKP rule packs and configuration outside of the wato directories | ||||||
| Date | Sep 3, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
With the global setting "Use GIT version control for Setup" enabled, only the
wato subdirectories below etc/check_mk/*.d/ were put under version control.
As a result the following Setup managed configuration was silently missing from the commits created on activate changes:
- Event Console rule packs that were made available for MKP packaging. Those are
stored in
etc/check_mk/mkeventd.d/mkp/rule_packs/. - Configuration files written directly into an
etc/check_mk/*.d/directory, for examplemultisite.d/sites.mkorconf.d/distributed_wato.mk.
Both are now tracked. On the first activate changes after the update the previously untracked files show up as a regular commit.
Everything that is not written by Setup stays excluded: the generated files
etc/check_mk/*.mk, the files managed by omd config
(conf.d/microcore.mk, conf.d/mkeventd.mk, conf.d/pnp4nagios.mk,
multisite.d/liveproxyd.mk, multisite.d/mkeventd.mk) as well as temporary
*.mk.new, *.pkl and swap files.
Note that multisite.d/sites.mk holds the automation secrets of the connected
remote sites. As with the already tracked conf.d/wato/passwords.mk, those
secrets now remain in the history of the repository even after a rotation. Keep
this in mind if you push this repository to a central GIT server.