Adding chroot_dir_manage parameter.

[Tamerz]

This PR adds a chroot_dir_manage parameter to the haproxy::instance and haproxy::config defined types.

I added it because the default permissions for the chroot directory on RHEL is owned by root. Changing it to the 'haproxy' user causes SELinux problems. I prefer leaving the directory owned by root.

[puppet-community-rangefinder]

haproxy::config is a type

that may have no external impact to Forge modules.

haproxy::instance is a type

that may have no external impact to Forge modules.

This module is declared in 40 of 578 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[puppet-community-rangefinder]

haproxy::config is a type

that may have no external impact to Forge modules.

haproxy is a class

Breaking changes to this file WILL impact these 10 modules (exact match):

• ploperations-haproxy_consul
• openshift-openshift_origin
• objectiflibre-ha_puppet
• pltraining-classroom_legacy
• narasimhasv-openstack
• puppetlabs-wordpress_app
• geoffwilliams-r_profile
• garystafford-haproxy_node_config
• spjmurray-puppet
• sdodson-openshift_origin

Breaking changes to this file MAY impact these 5 modules (near match):

• puppetlabs-peadm
• openstack-tripleo
• reidmv-pe_xl
• eshamow-pe_cert_auth
• eNovance-cloud

haproxy::instance is a type

that may have no external impact to Forge modules.

This module is declared in 40 of 578 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[CLAassistant]

All committers have signed the CLA.

[sheenaajay]

Thanks @Tamerz for submitting the PR.