-
Notifications
You must be signed in to change notification settings - Fork 54
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
⚠ Implement API changes according to RFC spec #1166
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR @jsm84 !
Requesting changes on my current comments. I'll be out tomorrow, so I'll circle around for further review on Monday.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1166 +/- ##
==========================================
- Coverage 77.55% 77.18% -0.38%
==========================================
Files 35 35
Lines 1916 1937 +21
==========================================
+ Hits 1486 1495 +9
- Misses 296 308 +12
Partials 134 134
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Just finished combing through the rest of the PR and I don't have any additional comments |
a991906
to
00528fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more comments on the comments. Overall I think they are good.
f188dd1
to
fe81727
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes looks good to me, thanks for the contribution @jsm84 !
I finished my review on mobile and it doesn't look like I can kick CI via the GH mobile app. I'll kick it first thing tomorrow morning and try to get this merged.
Closing and re-opening to try and reset the netlify checks that seem to be stuck |
resolves operator-framework#1088 Summary: * v1 API now uses a `SourceConfig` discriminated union which will allow modularity for future install sources (bundles, charts, etc). * `SourceConfig` uses CEL validation to ensure only valid field names & values are utilized (`sourceType: Catalog` ensures that the `catalog` field is also set in `SourceConfig`). * Added new `clusterextension_admission` unit test for `SourceConfig` objects. The test covers both valid and invalid cases. * Fixed `clusterextension_controller` test where an unset `ClusterExtension` spec caused a null pointer deref. * Moved `ClusterSelector` from `ClusterExtension.Spec` to `ClusterExtension.Source.Catalog` and renamed to `Selector`. * Updated GoDocs to reflect the new API spec and included post-review changes * Fixed all definitions of `kind: ClusterExtension` in docs and scripts to reflect the API changes. Signed-off-by: Josh Manning <19478595+jsm84@users.noreply.github.com>
fc888e5
resolves #1088
Summary:
SourceConfig
discriminated union which will allow modularity for future install sources (bundles, charts, etc).SourceConfig
uses CEL validation to ensure only valid field names & values are utilized (sourceType: Catalog
ensures that thecatalog
field is also set inSourceConfig
).clusterextension_admission
unit test forSourceConfig
objects. The test covers both valid and invalid cases.clusterextension_controller
test where an unsetClusterExtension
spec caused a null pointer deref.ClusterSelector
fromClusterExtension.Spec
toClusterExtension.Source.Catalog
and renamed to
Selector
.kind: ClusterExtension
in docs and scriptsto reflect the API changes.