I’m using a mix of Icinga Director and config management to push out Command configs and the recent update overlapped with some I had already created. That caused icinga2 to fail to restart (post update) and even after I fixed the overlap on the master and in Icinga Director, the changes couldn’t be pushed out since the satellites were not able to start. This led to me having to update /var/lib/icinga2/api/zones/global-templates/_etc/commands.conf manually on a bunch of servers. /gripe
I’m wondering if there is a better way to approach this or if there is another way to implement having a mixture of configs to avoid this type of issue. I don’t have the budget for a full fledged test environment where I could have seen this coming and changed my names first before the update was pushed.
Or is this just the unavoidable nature of having contrib configs as part of the icinga2-common package?
I suppose I could cherry pick configs I want out of the contrib dir and push them as needed, excluding the contrib from being imported by commenting out
Has anyone else run into this problem? If so, I’m curious how you are orchestrating these various levels of configurations.