[omd-users] Keeping WATO configuration in a Git repository

[Otterbein, Karl]

We  forklift the changes manually to my git repo.  Any changes we do post-base install, we effectively do via .mk files in puppet, test, and push to our Git repo, then do a puppet run to update and restart the cmk services.  I try to dissuade the use of WATO because we cannot replicate all changes if we had to do a site rebuild, and there is no source of truth once any person can manually update outside of Git.  This however would be a welcome function if plausible. 

-----Original Message-----
From: omd-users-bounces at lists.mathias-kettner.de [mailto:omd-users-bounces at lists.mathias-kettner.de] On Behalf Of Kim Tore Jensen
Sent: Thursday, September 18, 2014 11:02 AM
To: omd-users at lists.mathias-kettner.de
Subject: [omd-users] Keeping WATO configuration in a Git repository

Hi OMD users,

Has anyone successfully set up a system where all changes done through WATO are automatically committed to a Git repository, preferably on behalf of the current logged in (Multisite, using LDAP) user?

This would be a killer feature for our monitoring team.

Best regards,

Kim Tore Jensen