{"push_id":1145687535,"size":1,"distinct_size":1,"ref":"refs/heads/monitoring-config","head":"33eb00a2a105bc56350699141ed3540f1a3fec26","before":"66e146165802506a38aad01519ff7670ceef7afb","commits":[{"sha":"33eb00a2a105bc56350699141ed3540f1a3fec26","author":{"name":"Joel Diaz","email":"0a9d004c853c36de5b5f50006f01db0b3c8f06d5@redhat.com"},"message":"move monitoring container configuration into passed-in/bound file\nRather than pass numerous environment variable to control how the host-monitoring container is started/configured, move environment vars into a yaml file that can be bound in.\nThis will container things like the list of cron jobs to instantiate, the clusterid, zagg settings, etc. Logic that determines what gets installed is moved into the oso-host-monitoring role when it generates a monitoring-config.yml file for each node.\nConfig loop will now install /etc/openshift_tools/monitoring-config.yml, and the systemd file for host-monitoring will bind it in at the same location.\n\nFor local host-monitoring testing/development, create a reduced monitoring-config.yml which will not include Node/Master-specific checks (that will ultimately fail on a local environment).","distinct":true,"url":"https://api.github.com/repos/joelddiaz/openshift-tools/commits/33eb00a2a105bc56350699141ed3540f1a3fec26"}]}
{"actor":{"display_login":"joelddiaz"}}