8 commits

Author	SHA1	Message	Date
Mathieu Masse	dafe8fd6a5	Fix service state when override are used ... Service.running now uses correct require pkg id if haproxy.lookup.package is used Service.dead now uses correct name when haproxy.lookup.service is used	2018-03-22 20:43:25 -04:00
Eric Veiras Galisson	2b83ca0860	refactoring code to use map.jinja for config values ... at the moment only Debian managed, FreeBSD exception still in state	2017-10-31 14:41:54 +01:00
Konrad Mosoń	5b98ce8901	/etc/default/haproxy exists only on Debian-based distros ... Currently it's not possible to do `haproxy.service` on RedHat-based distros (like CentOS). Initscript doesn't use this file at all, so it's not needed to create it anyway. Actual result: ```---------- ID: haproxy.service Function: file.replace Name: /etc/default/haproxy Result: False Comment: /etc/default/haproxy: file not found Started: 16:16:46.775448 Duration: 2.19 ms Changes: ```	2015-11-13 16:49:53 +01:00
Nicolas Delaby	eb9c0c2b34	Allow usage of haproxy.service without haproxy.config	2015-10-02 00:45:56 +02:00
Adam Bolte	672fe36551	If not enabled in pillar, kill the service.	2015-07-23 13:46:56 +10:00
Adam Bolte	eb6b073ad2	Adjust ENABLED value based on pillar value.	2015-07-23 13:46:56 +10:00
Nicolas Delaby	1c541bd43d	Use reload instead of restart to prevent downtime during config updates	2015-03-17 17:35:21 +01:00
John Keates	3bc15512ae	Added jinja templated configuration support, a bit of documentation and a rough set of examples	2015-02-24 22:19:02 +01:00