This ensures that even if webhook is triggered multiple times when r10k is
already running, it would not fail as all requests to Sinatra server are serialised.

By default, this option is set to false. To enable this:

``` Puppet
class {'r10k::webhook::config':
enable_ssl => false,
use_mcollective => false,
enable_mutex_lock => true,
}
```

extra credit if you get the reference

Move enable_mutex_lock parameter into appropriate place in file

Add single request concurrency option in r10k webhook

Adding as @npwalker and other users don't Read the README and
instead just blindly cut and paste the examples. Mcollective is
required out of the box unless you disable.

create the /etc/puppetlabs/r10k directory

update plugins_dir for FOSS puppet

This will log at the 'error' level when r10k is not found in the PATH,
thus rendering the agent unusable.  Prior to this, Mcollective logging
would have to be set to 'debug', which would just return that the agent
failed to activate.  This commit hopes to provide more useful
information in this scenario.

If prefix is set to:
- true - env is prefixed with it's name
- false (default) - env is not prefixed
- custom string - this sting is used as a prefix

See:
https://github.com/puppetlabs/r10k/doc/dynamic-environments/configuration.mkd#prefix-behaviour

Log when r10k not found in PATH

Align webhook prefix command behavior with r10k behavior

configure forge settings with config class

Tags have no ref associated with them, so we cannot determine
programatically which branch to deploy. Instead, deploy the default
branch if one can be determined (github only) or deploy all
environments.

Prior to this, a release event would cause an HTTP 500 crash.

…like httpd prod tokens

…updating

postrun array requires spaces between elements

Grab the correct field for repo username

Handle tagged release events

adding server_software option to obscure the server software in use

According to
https://docs.puppetlabs.com/puppet/latest/reference/lang_reserved.html#environments,
environment names can only include lowercase characters *. As such,
downcase the environment we're trying to deploy, otherwise parts of the
PE stack can get quite cranky with you. This is a major change, though, so
default to the old behaviour of allowing uppercase names through.

* Empirically validated. The Puppet Master can handle uppercased
  environment names, but the Console (maybe other components as well)
  cannot. That means that the Console will assign the downcased
  environment name, which doesn't actually exist on disk :-/

Add option to lowercase environment names

Support for TFS/Visual Studio Git