-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add proxy usage for Windows agent install #547
Comments
To give more information, I tried forking your repo and change "pkg-windows.yml" file to use a proxy like that :
Changing this and running back my playbook command (ansible-playbook playbook.yml -i my-inventory -l myserver -f 5 --private-key my.key -u myuser -v -e HTTP_PROXY=http://proxy.fqdn:proxy.port/ -e HTTPS_PROXY=http://proxy.fqdn:proxy.port/) is working for an unauthenticated proxy usage. |
Hi @njt-cla 👋. I put together PR #553 that should help you - I'd be curious if you could provide feedback on it. First of all, it uses lowercase environment variable names (as recommended in official Ansible docs). Second, it also tells Ansible to omit the proxy_url value if http_proxy is not defined. Let me know if you think this makes sense, thanks! |
Hello, thanks for your fast answer. |
Hello,
I have tried to install Datadog Agent on a Windows Server that has no direct access to internet. It is available through a Proxy.
When trying to run the playbook to install Datadog Agent on a Windows Server, it fails because of this :
Your role is executed from this playbook (with a requirements.yml file that points on the main branch of this repository) :
The playbook is executed using this command :
These environment variables are visible in the Gather Facts command that runs at the beginning of the Playbook execution, but it is not used by the win_get_url module.
Is it possible to add a way to use a proxy in win_get_url commands you run for a Windows install ?
Thanks by advance.
Regards.
The text was updated successfully, but these errors were encountered: