Bug 1014047: need to create environment.conf when landing

[Dustin J. Mitchell]

Bug 1014047 deletes 'environment.conf' from the hg repo, and re-creates it as a puppet-managed file.

Unfortunately, between updating the hg repo on a master and running puppet on that master, 'environment.conf' is missing, and once the cache expires, you'll see errors about an import loop. If puppet runs on the master before that cache expires, all is well, but that's up to chance (10 minute cache, 30 minutes between puppet runs).

The fix is to add /etc/puppet/production/environment.conf with the following contents, after the hg repo is updated:

---
config_version = /etc/puppet/get_rev.sh $environment
manifest = manifests/site.pp
environment_timeout = 600s
---

Alternately, I used

cp /etc/puppet/production/environment.conf /tmp && /etc/puppet/update.sh && cp /tmp/environment.conf /etc/puppet/production/environment.conf

immediately after landing the change.

I've fixed this in the servo, moco, and relabs orgs.

Dustin