puppetlabs/Razor — pull request #208 by jamezpolley (2012-10-04 01:53:03+00:00)
Title: Update broker to handle puppet3.0

Spent some time this afternoon working with @nanliu to get the broker working with puppet3.0.

Pain points:

* The gem assumes that the puppet group exists before the group runs. As a workaround, we have the broker create the group before it tries to install the gem.
* The script uses ```set -e``` which causes it to abort when, for instance, ```puppet agent -t``` returns an exit status of ```2```, indicating that some resources changed.
* In order to make troubleshooting easier, we capture the output of ```puppet_init.sh``` and store it on the node, alongside ```puppet_init.sh```

We also removed the ```nohup puppet agent```. By the time the script gets to that point, it should already have applied the initial configs. If we want puppet to be running, puppet can configure that itself, via whatever method we want.