Section Number and Name:
3.4. Configuring Satellite Server with an HTTP Proxy
Describe the issue:
In satellite 6.7 we are dropping the ability to set the global content syncing proxy via the installer.
Suggestions for improvement:
Suggest using hammer to create the proxy and set it to the global proxy after the installer runs:
hammer http-proxy create --name=myproxy --url http://myproxy:8080 --username=proxy_user --password=proxy_password
hammer settings set --name=content_default_http_proxy --value=myproxy
note i pointed to the 6.6 docs, but the change needs to occur for 6.7
*** Bug 1812852 has been marked as a duplicate of this bug. ***
Sergei, happy to talk to you as soon as possible. Let's figure out a good time to discuss, if you want. Or I can just reply here with my comments.
I see you have a busy schedule today. Please reply in a bug for now.
Please review this PR where I updated docs with new steps for configuring HTTP proxy:
Did you find something out regarding the reset options?
The reason there was a special way to 'reset' was because it was hard to do that with the installer. Now that its not based on the installer, you can simply unset the global setting to remove the global default, or delete the HTTP Proxy within the 'Infrastructure > HTTP Proxies' section.
One thing to add to the docs is the per-repository setting:
This allows more fine grain control, to set a repository to use the global proxy, override it to use no proxy at all, or override it to use a specific proxy.
thank you for the reply, I have updated the PR with the commit that fixed the instructions to reset the HTTP proxy setting,
As for the per-repository settings, they are covered in 5.11. Changing the HTTP Proxy Policy for a Repository:
This looks correct to me. Thanks!
The changes are live upstream and are live on the 6.7 branch to be published with the Satellite 6.7 GA release.