search

NagiosEnterprises / ncpa

Nagios Cross-Platform Agent
Other
176 stars 95 forks source link

NCPA Linux update is fragile #1057

Open shodgson11 opened 7 months ago

shodgson11 commented 7 months ago

Every time NCPA updates it pauses the apt upgrade process waiting for user input (even when run with apt upgrade -y).

This also leads to some users who don't know any better selecting to use the new config file which wipes out the NCPA community_string and breaks communication with Nagios XI. What can be done to avoid this situation on future NCPA updates? If we keep our existing file, then we miss any new configurations added. This is a bad update experience for all available choices.

The only custom change in my config file is setting the community_string.

shodgson11 commented 7 months ago

Seems like this could be solved by using an override config file that takes precedence over the standard config file when present. This wouldn't interrupt the update process since the installed config file wouldn't change and it would maintain the user-specified config entries as well.

everwatch commented 7 months ago

Files in the /usr/local/ncpa/etc/ncpa.cfg.d directory named *.cfg will be parsed (in order by filename) and merged with ncpa.cfg. You should be doing site-customization in local [managed] files in this directory instead of modifying the master ncpa.cfg file.