Skip to content

support cacheless catalogsources #3257

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

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

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

grokspawn commented May 15, 2024

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
@grokspawn grokspawn added this to OLM Apr 21, 2025
@github-project-automation github-project-automation bot moved this to Backlog in OLM Apr 21, 2025
@grokspawn grokspawn moved this from Backlog to In Progress in OLM Apr 21, 2025
@grokspawn grokspawn moved this from In Progress to Done in OLM May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic An umbrella issue that encompasses several related issues
Projects
Status: Done
Development

No branches or pull requests

1 participant