Currently you can utilize GOLang's support for HTTP_PROXY/HTTPS_PROXY environment variables but they must be configured in the session/context that the daemon is launched under.
It would be valuable to be able to configure these as part of the daemon JSON such that you can deploy all of your engine's with the same configuration without needing additional configuration scripts or systemd/windows configuration.
One approach for this might be to read the values in at launch time and set the appropriate locally scoped environment variables or there may be other GoLang support for these options as this point.
Currently you can utilize GOLang's support for HTTP_PROXY/HTTPS_PROXY environment variables but they must be configured in the session/context that the daemon is launched under.
It would be valuable to be able to configure these as part of the daemon JSON such that you can deploy all of your engine's with the same configuration without needing additional configuration scripts or systemd/windows configuration.
One approach for this might be to read the values in at launch time and set the appropriate locally scoped environment variables or there may be other GoLang support for these options as this point.