Changing default version to 0.4.0

Issue copy-paste from
#16

When you install letsencrypt using the VCS method, it will create a
virtualenv, which would normally be located in
~/.local/share/letsencrypt:

Excerpt from letsencrypt-auto:
```
XDG_DATA_HOME=${XDG_DATA_HOME:-~/.local/share}
VENV_NAME="letsencrypt"
VENV_PATH=${VENV_PATH:-"$XDG_DATA_HOME/$VENV_NAME"}
```
However, puppet exec's will not set $HOME, which will stop Debian's
/bin/sh, dash, from expanding ~, so it creates a literal '~' folder.

Issue copy-paste from
#16

When you install letsencrypt using the VCS method, it will create a
virtualenv, which would normally be located in
~/.local/share/letsencrypt:

Excerpt from letsencrypt-auto:
```
XDG_DATA_HOME=${XDG_DATA_HOME:-~/.local/share}
VENV_NAME="letsencrypt"
VENV_PATH=${VENV_PATH:-"$XDG_DATA_HOME/$VENV_NAME"}
```
However, puppet exec's will not set $HOME, which will stop Debian's
/bin/sh, dash, from expanding ~, so it creates a literal '~' folder.

Using the `cron_success_command` parameter for `certonly`, you can
run commands when the renewal command was successful, e.g.
reload the webserver to use the renewed certs.

Not sure about letsencrypt return values, so the command might be
executed even if the cert is unchanged, doesn't matter for this
usecase though.

Fix #16 by specifying VENV_PATH when running letsencrypt.

For at least some kind of security...

Update client

Fixing test failures when STRICT_VARIABLES is set to true

So we avoid fiddling with the venv every time, and the cron is now
silent.

refs GH-26

Split letsencrypt commands, so -auto is only used once

concat to throw errors!)

Added optional 'environment' parameter to init and certonly. Specced.

… into cron_success_cmd

Conflicts:
	manifests/certonly.pp
	manifests/init.pp
	manifests/params.pp

…ncrypt::certonly

Closes #18: merging @mheistermann's changes

Defaults for el7

This change adds package_name and package_command params
and as a bonus support for Gentoo. Test for this use case
was also created.

Name and command params default to their old values,
so change should be fully backward compatible.

Add a way to change package name and command

certbot has replaced letsencrypt in EPEL7:
https://apps.fedoraproject.org/packages/certbot
https://apps.fedoraproject.org/packages/letsencrypt

Change EL7 package and command to certbot

Various smaller fixes.

Fix validation of letsencrypt_command

Fixes GH-37

Validate presence of webroot_paths with webroot plugin

When fewer webroot_paths than domains are supplied, certbot/LE will use
the last webroot path given rather than the module cycling through
webroot_paths. When webroot_paths is one element, there will be no
behaviour difference.

Fixes GH-28

Remove webroot_paths cycling to match domains list

We can't upgrade beyond 1.0 series without either dropping tests using
puppet-lint-filerserver-check, or waiting for the author of that Gem to
merge in a fix for the dependencies:
camptocamp/puppet-lint-fileserver-check#2

To avoid breaking tests of this module meanwhile, we shall pin.

…n function and believes we are calling a class. Mark it as OK.

Puppet 3.x series with Puppet 2.2+ is not compatible since Puppet ships
a YAML parser that no longer functions on that Ruby version. Best to
remove them entirely from the build matrix so we don't test impossible
combinations.