system-config/run_all.sh
Monty Taylor 21ab83c0b5 Add some system logging to run_all
When we want to watch run_all happen, it's hard, because there is
no logging. To fix that - make there be some logging. Then, rotate
the logs.

Change-Id: I0eed7aeeec0ff21e58d57d6385cc59b74bbf31fb
2014-04-18 14:16:16 -07:00

30 lines
1.0 KiB
Bash
Executable File

#!/bin/bash
# Copyright 2014 Hewlett-Packard Development Company, L.P.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
cd /opt/config/production
git fetch -a && git reset -q --hard @{u}
./install_modules.sh
# One must touch manifests/site.pp to trick puppet into re-loading modules
# some times
touch manifests/site.pp
# Put in a logging header
echo "****\n\n$(date)\n\n****" >> /var/log/puppet_run_all.log 2>&1
# Run this as an external script so that the above pull will get new changes
/usr/local/bin/run_remote_puppet >> /var/log/puppet_run_all.log 2>&1