Is your feature request related to a problem? Please describe.
Currently, if we don't set any http/https proxy on the MQTT Client Options, related http and https proxy settings are taken from the environment variables, which de-facto standard environment variables as presented in the nice article from Gitlab guys: https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/
However, as current library is not considering NO_PROXY environment variable on our client settings, which basically leads to introducing additional logic or special docker configurations on our development or testing environments.
Describe the solution you'd like
Right thing is to consider also NO_PROXY environment variable on proxy settings of the MQTT Client Options, where if endpoint is in the list of the NO_PROXY, proxy settings will be ignored automatically.
Is your feature request related to a problem? Please describe. Currently, if we don't set any http/https proxy on the MQTT Client Options, related http and https proxy settings are taken from the environment variables, which de-facto standard environment variables as presented in the nice article from Gitlab guys: https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/ However, as current library is not considering NO_PROXY environment variable on our client settings, which basically leads to introducing additional logic or special docker configurations on our development or testing environments.
Describe the solution you'd like Right thing is to consider also NO_PROXY environment variable on proxy settings of the MQTT Client Options, where if endpoint is in the list of the NO_PROXY, proxy settings will be ignored automatically.