Bug 1332328 - [RFE] repodiff is not able to compare repos that require certificate authentication (redhat, satellite, etc.)
Summary: [RFE] repodiff is not able to compare repos that require certificate authenti...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum-utils
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-02 23:33 UTC by Justin Garrison
Modified: 2019-01-03 12:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 12:32:08 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Justin Garrison 2016-05-02 23:33:59 UTC 
Description of problem:
allow repodiff to accept authentication certificates for repo urls.

Version-Release number of selected component (if applicable):
0.2

How reproducible:
Always

Steps to Reproduce:
1. Try to use repodiff against https://cdn.redhat.com/.../repo

Actual results:
Permission denied on the repo because it requires certificate (key and cert) authentication.

Expected results:
Allow some way to specify --cert --key for accessing the repositories to see if there are changes with local mirrors.

Additional info:
Comment 1 Justin Garrison 2016-05-02 23:39:11 UTC 
It could also be useful if I could specify a repo by name from yum repolist. Ideally it would just use the configuration for that repo defined in the .repo file.

That could possibly simplify the cli syntax for repodiff.

e.g.

repodiff --old-name /some/mirror/path --new-name rhel-7-server
Comment 4 daniel.souvignier 2017-09-19 09:47:46 UTC 
I second this. Would be great to have (also usable for ULN then).
Comment 6 Daniel Mach 2019-01-03 12:32:08 UTC 
This bug no customer case attached and wasn't proposed for the next minor release.
There is no plan to fix it in RHEL 7.
Note You need to log in before you can comment on or make changes to this bug.