-
Notifications
You must be signed in to change notification settings - Fork 73
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
🐛 fix ClusterServiceVersion CRD Generation #324
🐛 fix ClusterServiceVersion CRD Generation #324
Conversation
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #324 +/- ##
=======================================
Coverage 39.43% 39.43%
=======================================
Files 56 56
Lines 4516 4516
=======================================
Hits 1781 1781
Misses 2581 2581
Partials 154 154 ☔ View full report in Codecov by Sentry. |
It seems like |
I think we can override the verify here. It seems like there's been a change in the go doc for json.RawMessage:
https://github.com/golang/go/blob/release-branch.go1.22/src/encoding/json/stream.go#L255 This is changing the field description and causing verify to fail |
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
eb2af81
to
78fb217
Compare
Thank you! I was chasing a different issue. Let's see if verify clears it (it will fail for the reasons I stated above in olm)... |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: m1kola, perdasilva The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold Want to check one thing before we merge |
/unhold |
/hold - let's see if the kind job in the other PR fails first - then merge, and see if it succeeds =D |
/unhold |
New API updates is tripping up more validations against default values in the Deployment stanza of the CSV. This PR adds a couple of yq replacement queries to add default values to those fields.
seems the crds/zz_defs.go was also out of sync - regeneration seems to have fixed it