make it future parser compatible

Merge 1.2.x to master

Remove extraneous spaces. Update tests to reflect change.

This patch updates raise_error and params_value to use `catalogue`
instead of `subject` since the contents of `subject` aren't evaluated
the way they used to be. Also, since the future parser considers empty
string to be a truthy value, and then interprets two incompatible
parameters to both be set if one is an empty string, it removes the
unset ipaddress parameter from one of the tests. Finally, it unpins
rspec-puppet.

puppetlabs_spec_helper handles these dependencies for us.

The modulesync config repo is dropping universal support for puppet
2.7, but individual repos should still keep support until the next
naturally-occuring major release.

This commit makes the following changes to the test matrix:

- Runs tests on ruby 2.1.5 instead of 2.0.0
- Runs tests on ruby 1.8.7 with puppet 3.x
- Adds an environment to run on an intermediate 3.x puppet version
  instead of latest (specifically 3.4.x)
- Adds an environment to run with the future parser on latest puppet.
  This would affect the test runs for the validate and spec checks.
- Runs the tests on docker

puppetdb, etc

- support for BEAKER_VERSION and BEAKER_RSPEC_VERSION in gemfile

(BKR-147) add Gemfile setting for BEAKER_VERSION for puppet...

(WIP) Testing updates

Fixes https://tickets.puppetlabs.com/browse/MODULES-1317. See also the
discussion in PR #171.

Frontend, backend and listen options are specified via the
`haproxy::frontend::options`, `haproxy:backend::options` and
`haproxy::listen::options` parameters. Until now this `options`
parameter was a hash, which means it had to be sorted before processing
it in the `_options.erb` template fragment (since Ruby 1.8.x has
non-deterministic hash key ordering).

This clashes with the fact that in HAProxy's configuration order matters.

With this change we allow the `options` parameter to be either a hash,
like before, or an array of hashes, where each hash represents a
frontend, backend or listen option and its value. This way the order in
which options will appear in the final configuration file can be
controlled entirely by the user.

This change is completely backwards compatible and contains updated spec
tests and documentation.

Implement `options` as array of hashes so order is preserved

fixing lint issues

gentoo compatibility

* commit '33ceaf932fb694e54fc3d917580e2c89e40f0ae7':
  adding unit tests, removing official support.
  gentoo compatibility

Adds documentation to peer and peers resource types

Modulesync updates

1. Remove any "what this affects" sections, except where particularly warranted.
2. Make sure that for each parameter, where applicable, there is a data type and a default value.
3. Make sure that for each parameter that's applicable, there is a note if the parameter is optional.
4. Make sure the links in the README work and are accurate.
5. Update the link in the Contributing section to point here: https://docs.puppetlabs.com/forge/contributing.html
6. General copyediting.

Add Usage subsections back to the table of contents
Add back language syntax highlighting to fenced code blocks.

Rewrite README per DOC-1499

Add Suse to list of supported OSes

ignore the log directory

changes to fix puppet4 unit tests

need to allow both commands to run more than once

relax unit test for puppet 2.7

Updated travisci file to remove allow_failures on Puppet 4

…rsion

(maint) allow setting PUPPET_VERSION in acceptance

Add helper to install puppet/pe/puppet-agent

Release 1.3.0