Aleks

I fully agree to the previous comments. helm should have the option to use environment variables maybe with a flag `--I_really_know_what_I_m_doing`

As it sounds like a good Idea it's not a easy task :smile: . As I'm a fan of the [KISS Principle](https://en.wikipedia.org/wiki/KISS_principle) my current workflow is this and I'm quite...

This variable is used when the `printf()` is executed https://github.com/haproxy/haproxy/blob/master/src/mjson.c#L190 Can we make this as false positive or how to go further with this topic

Okay, where should the pragma be set?

Thank you for your suggestion. I have created a Issue in the upstream code https://github.com/cesanta/mjson/issues/51 , please let us wait for the answer from the upstream author to fix this...

Is the `openssl engine` https://cbonte.github.io/haproxy-dconv/1.9/configuration.html#ssl-engine with https://github.com/OpenSC/libp11 not a possible solution for your use case? Maybe this issue thread help you to create a solution https://github.com/OpenSC/libp11/issues/160

@type4ranjan maybe you can create a patch and contribute to HAProxy :smile: Please take a look into the https://github.com/haproxy/haproxy/blob/master/CONTRIBUTING file for contribution

Well https://github.com/DBezemer/rpm-haproxy/releases provides also rpm packages even the latest one :-)

Yep there is no "QUIT" in the check https://github.com/haproxy/haproxy/blob/master/src/tcpcheck.c#L4234 You can create your own smtpchk with a explicit QUIT. Something like this, untested. ``` tcp-check connect default linger tcp-check expect...

> However, given that "smtpchk" is designed to be a quick "one stop shop" method for generating SMTP checks without lots of tcp-check lines, I believe there is a valid...