After Ranch (socket acceptor pool) has come into effect
the following tcp listen options is no longer valid:
  - binary, packet, reuseaddr.

For details:
rabbitmq/rabbitmq-server#260

It is an equivalent of curl_option='-k'.

Puppetlabs Apt module now has deprecation warnings when call in the manner being used by the puppetlabs rabbitmq module. Updated and tested against puppetlabs apt module 2.2.2

This resolves a bug when queue names have spaces in them the splitting doesn't work as expected

Allows deprecation errors

Fix sync

(MODULES-3704) Update gemfile template to be identical

Designate former tests files as examples

(MODULES-3631) msync Gemfile for 1.9 frozen strings

(FM-5939) removes spec.opts

(FM-5972) gettext and spec.opts

These options are used for RabbitMQ to create a TCP listener, which is
not something we want if we are doing SSL-only. So these are not used as
defaults if that option is set.

The rabbitmqadmin CLI tool added better SSL support since version 3.6.2 and allows to set a few more CLI parameter. This puppet module does not incorporate these options when instrumenting the rabbitmqadmin tool. Therefore these options are now added to the config template and set appropriately when ssl is enabled. For earlier versions of RabbitMQ the new options are ignored by the admin tool and should not cause any errors.

(MODULES-4097) Sync travis.yml

(MODULES-4098) Sync the rest of the files

the parallel_spec that is run on travis revealed a dependency issue in the user_permissions_spec. none of the type unit tests were using the spec_helper and were requiring puppet and their respective types explicitly. this reverses that by requiring the spec_helper and removing the other dependencies and in turn repairing the failures.

(maint) parallel_spec maintenance: spec_helper

Cleanup void tcp options

Signed-off-by: Kenny Van de Maele <vdmkenny@inuits.eu>

added ssl_depth and password params for configuration

As per a recent commit [1], the default value of ssl_depth is undef.
This turned out problematic, as the template checks for 'UNSET', and
validation of this parameter is only done if the ssl_depth was set to
something (remember it defaults to undef). So, using the default value
results in an invalid rabbitmq configuration, which breaks with a syntax
error.

This sets the check in the template to work only if the value of that
variable is set (so it won't write it if the default undef is used).

[1] 21ac01e

…s increases compatibility with Xenial

[MODULES-4450] don't set ssl depth if undef

[MODULES-4223] don't set NODE_PORT and NODE_IP_ADDRESS if ssl_only