Automate rebuilding the contributor list

This extends the hacks in the Modulefile to automatically rewrite the
contributor list in a stand-alone file.  This makes it practical to give
public credit to the folks who have contributed to the module without human
error dropping some of them.

Closes #122.

Signed-off-by: Daniel Pittman <daniel@puppetlabs.com>
Make `tar` installation of stable releases the default

This moves away from the previous, legacy, default of installing from git
head, in favour of installation from the stable release tar file available on
https://downloads.puppetlabs.com/razor

Like the packages, this will refuse to install over the top of an existing git
deployment; if `/opt/razor/.git` exists the Puppet module will refuse to run.
Users should manually remove the directory - or otherwise resolve
the conflict.

It is safe, and supported, to simply delete the `.git` directory, and then
install from tar over the existing git deployment.  There should not be any
data loss from this.

This closes #124.

Signed-off-by: Daniel Pittman <daniel@puppetlabs.com>
Merge pull request #123 from daniel-pittman/feature/master/122-automate-the-contributor-list-in-readme-md

Automate rebuilding the contributor list
Merge pull request #125 from daniel-pittman/feature/master/124-make-default-install-method-user-friendly-not-user-hostile

Make `tar` installation of stable releases the default
Fix missed use of `git_version` parameter in specs

Pull request #125 removed the ability to specify a git source or revision,
along with other changes; this wasn't reflected in the tests.

This strips out the attempt to use the git version, which wasn't providing any
particular value in any case.

Signed-off-by: Daniel Pittman <daniel@puppetlabs.com>
Merge pull request #126 from daniel-pittman/bug/master/broken-spec-after-125-merged

Fix missed use of `git_version` parameter in specs
Revert "Make `tar` installation of stable releases the default"

This reverts commit 9ea9092c300df325bb3eb1867281442a109b0fd0.

It turns out that the approach I took to solving the problem, while
attractive, is secretly an attractive nuisance.

It makes it impossible to actually test anything but the released version of
the code and, in the nature of hitting commit, also called a couple of people
out to explain why it made their lives miserable also.

This brings us back to the previous state, from which I will proceed forward
to add tarball support again, and to integrate it in a fashion that doesn't
lead to quite the same set of failures.
(#130) Razor providers should check return value for errors

This change modifies the create and destroy methods in the rz_broker,
rz_image, rz_model and rz_policy providers to raise a Puppet::Error
when an error occurs. This is achieved by passing the output to the
parse method in the PuppetX::PuppetLabs::Razor class. If the output
contains a 'response' key, it is returned, if it contains a 'result' key,
a Puppet::Error exception is raised with it, otherwise a Puppet::Razor
exception is raised with the whole output.

The reason for this change is to enable Puppet manifests using
Razor resources to actually get an error when the razor command
fails. Otherwise, the error is simply ignored and the user has to
reverse engineer the problem from the side effects of the failure.

Note that this change moves the parse method in PuppetX::PuppetLabs::Razor
from being private to public, so that it can be re-used in the
providers. Also note that it did not implement the behavior for the rz_tag
provider because it is much more complicated, having to potentially
manage multiple tags. This can be handled in a separate pull request.

This pull request fixes issue #130.
Merge pull request #131 from cr3/130

(#130) Razor providers should check return value for errors
(#133) Razor image provider should not check for errors like other providers

This change reverts checking for errors in the image provider because
the image action of the razor command does not return PSON unlike the
other actions. Instead, the image provider now returns the output of
the razor command and always succeeds, like before.

Ideally, the image provider should look at the return value and raise a
Puppet::Error when failing to add an image. However, the razor command
always seems to return 0 and the output is awkward to parse. So, the
changes to the image provider should be reverted for now until the Razor
project is updated accordingly.

Closes #133
Merge pull request #134 from cr3/133

(#133) Razor image provider should not check for errors like other providers