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

Operator-Controller resolution considers spec.channel #170

Closed
Tracked by #163
awgreene opened this issue Apr 17, 2023 · 0 comments · Fixed by #172
Closed
Tracked by #163

Operator-Controller resolution considers spec.channel #170

awgreene opened this issue Apr 17, 2023 · 0 comments · Fixed by #172
Assignees
@tmshort
Labels
olm-v1/m3
Milestone
v0.1.0 (OLMv1 Mil...

Comments

@awgreene
Copy link
Member

Goal:
The Operator Controller should be updated to feed channel constraints into Deppy.

Background:

  • When working on this ticket, it may be fruitful to review this PR, which updated the operator API to allow users to specify a spec.version constraint.

Acceptance Criteria:
@joelanford joelanford mentioned this issue Apr 17, 2023
Closed
2 tasks
@joelanford joelanford added this to the v0.1.0 (OLMv1 Milestone 3) milestone Apr 17, 2023
@tmshort tmshort self-assigned this Apr 17, 2023
@tmshort tmshort mentioned this issue Apr 18, 2023
Merged
tmshort added a commit that referenced this issue Apr 21, 2023
@tmshort
Handle channelName (#172)
4cd2f82 
Adds backend support for channelName

Fixes #170
Fixes OPRUN-2917

* Integrate channelName
* Add channelName unit tests
* Update error messages
* Update channel name regex

Signed-off-by: Todd Short <tshort@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tmshort tmshort

Labels
olm-v1/m3
Projects
None yet
Milestone
v0.1.0 (OLMv1 Milestone 3)
Development

Successfully merging a pull request may close this issue.

Handle channelName tmshort/operator-controller
3 participants
@joelanford @awgreene @tmshort