Comment 6 for bug 1475946

We use modified version of upstream module to utilize ability of using 'conf.d' directory for haproxy. It is very convenient for us and we built custom haproxy package for every Fuel release because of it. Those patches will never be in upstream haproxy (it was discussed three or four times with haproxy developers), so our patches for puppet module will never be in upstream also. So, we have two options:

1. Use our changes rebasing them time to time to upstream master.
2. Drop our changes and refuse of ability using 'conf.d' for haproxy.