-
Notifications
You must be signed in to change notification settings - Fork 545
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
Remove CatalogSourceLister usage from resolver/cache. #2648
Remove CatalogSourceLister usage from resolver/cache. #2648
Conversation
Ah, it looks like approval-acts-as-lgtm doesn't work on this repository. /lgtm |
b4874f0
to
0ed9044
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, njhale, timflannagan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Let's get #2625 merged first. /hold |
The cache hardcodes the use of a CatalogSourceLister (imported from a non-resolver package in the OLM module) in order to assign source priorities based on the spec.priority field of CatalogSource. Not all cache sources map to a CatalogSource, so this can instead accept a priority provider interface and the resolver -> non-resolver imports can be removed. Signed-off-by: Ben Luddy <bluddy@redhat.com>
0ed9044
to
48984bd
Compare
/hold cancel |
/lgtm |
The cache hardcodes the use of a CatalogSourceLister (imported from a
non-resolver package in the OLM module) in order to assign source
priorities based on the spec.priority field of CatalogSource. Not all
cache sources map to a CatalogSource, so this can instead accept a
priority provider interface and the resolver -> non-resolver imports
can be removed.