9.3.1. Upstream GIT Repository
Using the upstream GIT repository, you can choose between different upstream branches; development, testing, or production. These branches correspond with the environments the puppetmanaged.org puppetmaster offers to it's clients.
The workflow in upstream GIT repository branches allows changes to first be applied to the development, then tested on a system that runs only this module, to see if the module itself works as expected. If the changes work as anticipated, they are pulled into the testing branch, and tested in conjunction with other modules (which may have changed as well) using a system that runs against the testing environment. If all is well, changes are pulled into the production branch.
We recommend that if you do not use staging, you use the production branch of the module. However, changes to the production branch are not applied as rapidly compared to the development branch.
To obtain a clone of the GIT repository, use:
$ git clone git://git.puppetmanaged.org/puppet/git
Then, checkout the branch you want to use, if not development:
$ cd git/
$ git checkout --track -b production origin/production
9.3.1.1. Automatic Updates
If you used GIT to clone the repository, you can then use GIT to obtain updates to that module (and it's branches) by using:
9.3.1.2. Fully Automation
Using the same method as the puppetmaster from puppetmanaged.org, you can also enable full automation. This includes offering three separate environments to the nodes, but it's up to you which environment is actually used.
Requires puppet-module-git (this module)
Requires environment staging
Requires patience
