As a user, I can conveniently define global importer settings
Pulp RPM importer lacks (IMO) key functionality of a "no_proxy" key-value pair to go alongside the existing proxy-related key-value pairs.
Within enterprises that employ a proxy at the border that doesn't loop back into the border for local traffic, Pulp / Satellite 6 customers have to make the choice of syncing only external content (cdn.redhat.com / epel mirrors) or internal content.
Pulp should allow per-repository proxy values, or should globally employ a "no_proxy = *.mycompany.com" coping scheme to allow those with strict border proxies a way to effectively use Pulp / Satellite 6.1+.
#1 Updated by kfiresmith over 4 years ago
Posted to the mailing list to get a sanity check that I've not somehow missed something and this functionality already exists - I'll come back and close this if it turns out I just missed something simple...
For the Red Hatters here, I'm a paying customer and have also lodged CASE 01506495 with Red Hat support. We can't really use Satellite 6 until this is sorted.
#2 Updated by kfiresmith over 4 years ago
#3 Updated by mhrivnak over 4 years ago
- Tracker changed from Issue to Story
- Subject changed from No RPM importer support for "no_proxy" key-value to As a user, I can conveniently define global importer settings
- Groomed set to No
- Sprint Candidate set to No
Thank you for pointing this out. We need to re-think how we define proxies and other importer settings, and associate them with specific repos.
It is likely that as a direct user of pulp, you could set the proxy settings to None for the individual repos that you don't want to use the proxy. Then katello/satellite could potentially make use of that.
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue