Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support cacheless catalogsources #3257

Open
2 tasks
grokspawn opened this issue May 15, 2024 · 0 comments
Open
2 tasks

support cacheless catalogsources #3257

grokspawn opened this issue May 15, 2024 · 0 comments
Labels
epic An umbrella issue that encompasses several related issues

Comments

@grokspawn
Copy link
Contributor

With commit of operator-framework/operator-registry#1278, pre-generating catalog caches should no longer be necessary (once it releases and dependencies here are updated to use the new release).

To support cacheless catalogs, we need to

  • make extractContent.cacheDir optional here
  • update reconciler code to handle the optionality here
@grokspawn grokspawn added the epic An umbrella issue that encompasses several related issues label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic An umbrella issue that encompasses several related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grokspawn