This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
haproxy.ssl-verify doesn't like being false #117
Comments
|
The Prometheus project switched to kingpin, which has a rather unique opinion on boolean flags https://github.com/alecthomas/kingpin#boolean-values. Thanks for catching this, wanna send a PR? |
|
Super quick response, thanks! That worked, will get a PR worked up shortly. |
Merlin83b
added a commit
to Merlin83b/haproxy_exporter
that referenced
this issue
Jun 21, 2018
Change as per prometheus#117 Signed-off-by: Daniel Foster <daniel@df.me.uk>
Merlin83b
added a commit
to Merlin83b/haproxy_exporter
that referenced
this issue
Jun 21, 2018
Change as per prometheus#117 Signed-off-by: Daniel Foster <merlin83b@users.noreply.github.com>
|
Third time lucky! |
grobie
pushed a commit
that referenced
this issue
Jun 21, 2018
Change as per #117 Signed-off-by: Daniel Foster <merlin83b@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As per the README.md, I set haproxy.ssl-verify to false:
./haproxy_exporter --haproxy.ssl-verify=false --haproxy.scrape-uri=...(with a valid URI) and got the following error:
haproxy_exporter: error: unexpected false, try --helpChanging the URI to one that does have a valid SSL cert fixes this, but wasn't what I wanted to do.
The text was updated successfully, but these errors were encountered: