We need to verify we are in compliance
created nagiosdaemon user with permissions to monitor license status as well as standard monitoring
added credentials to hiera Committed revision 92064.
This change broke all the production postgres checks. There was already a secrets_nagiosdaemon_postgres_username and secrets_nagiosdaemon_postgres_password that was being used. revision 92064 duplicates the declaration and broke production runs.
I looked at adjusting the change and fixing it, but I didn't see the secrets_nagiosdaemon_postgres_password in use anywhere other than the declarations I made in the postgres module (they weren't in use on the vertica module). Because I didn't see a way to fix it I rolled back that commit and removed the duplicate declarations from site.yaml.
I made the mistake of using postgres when I meant to use vertica in the naming convention, I have readjusted and apologize for the broken production runs
changed made in Committed revision 92079
No worries. :) I'd have fixed it for you if I could find where they were called from. It didn't cause that much of an issue, just a rather unexpected 20 pages. Glad to see it's fixed.
Is this check complete now?
This check is not a priority as we are in our last year with Vertica. Taken out of nagios in r101122 and out of nrpe in r101123.