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.

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

Reduce number of variables involved in resolution process #494

Closed
m1kola opened this issue Oct 31, 2023 · 1 comment
Closed

Reduce number of variables involved in resolution process #494

m1kola opened this issue Oct 31, 2023 · 1 comment

Comments

@m1kola
Copy link
Member

m1kola commented Oct 31, 2023

Spinning out of #437

We need to explore if we can reduce number of variables involved in resolution.

Today we have the following variable types:

  • RequiredPackageVariable - variable for what an user explicitly requested via Operator API. It contains constraints for potential candidates for installation.
  • InstalledPackageVariable - variable for what we already have on the cluster. It contains constraints for potential successors of the currently installed bundles.
  • BundleVariable - variable for each bundle involved in resolution. It contains constraints for depenencies of the bundle.
  • BundleUniquenessVariable - variable that contains constraints to restrict the solution to at most a single bundle per package.

We need to look into whether we can combine some of the variables together.

Previous discussion on this: #460 (comment)

@m1kola
Copy link
Member Author

m1kola commented May 3, 2024

No longer applicable since we removed Deppy

@m1kola m1kola closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant