Description of request; Add an optional field in registration to add a --noproxy to pass to the curl commands so that any proxy defined in system env variables are ignored when going to the Satellite or other URL provided.
Can you please describe more in detail how the registration should behave?
I guess that may require "Ignore system proxy configuration" checkbox. If checked, it would pass this --noproxy to all curl commands used during the registration template.
Hi Leos, Marek, Right, that's the idea, to add a checkbox that will be optional that, when checked, will add the --noproxy option on the curl command(s) in the registration template. The template can be customized to add this at the moment, but having the option built in will be convenient for the customer. I believe this can be a simple checkbox that automatically passes the @rhsm_url.host to --noproxy, but there are perhaps other more convenient ways of doing it. This assume the scenario of the following; The user has an environment where systems need a proxy for outside contact, so the proxy env variables are always set. They do not need the proxy to reach the Satellite, so during normal registration these vars get in the way. Adding an optional checkbox to pass --noproxy <registration host> to the curl command will help prevent users from having to edit the curl during each generation of the command, or altering the template themselves for only this purpose.