Skip to content

Convert Operator CR into Deppy Constraints #70

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
awgreene opened this issue Dec 7, 2022 · 1 comment
Closed

Convert Operator CR into Deppy Constraints #70

awgreene opened this issue Dec 7, 2022 · 1 comment
Assignees

Comments

@awgreene
Copy link
Member

awgreene commented Dec 7, 2022

User Story:

As a user, I would like the packageName I specify in the Operator Controller to be converted into a Deppy Constraint.

Background:

  • The goal of this story is to convert an Operator CR into Deppy Constraints.
  • Today, we only plan to introduce the packageName and GVK constraints, but will expand in the future.
  • Within the context of Deppy, Variables are logical statements that can be true or false. Constraints are variables that must be true in a solution set. So for this story:
    -- The user will specify a package that they want to install within an Operator CR's spec.PackageName field
    -- The operator controller will create a "Deppy Variable" that captures this packageName constraint.
    -- The Deppy Library will introduce the GVK Uniqueness requirement.

Acceptance Criteria:

  • An Operator CR can be converted into a set of Deppy Constraints.
@perdasilva
Copy link
Contributor

#105 closes this issue

@github-project-automation github-project-automation bot moved this from Todo to Done in OLM v1 Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants