-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Drop the use dprotaso/controller-tools fork #15664
Conversation
cc @skonto I need to revisit some new attributes that were added so marking WIP for now |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15664 +/- ##
==========================================
- Coverage 83.48% 80.75% -2.74%
==========================================
Files 219 222 +3
Lines 17432 18024 +592
==========================================
+ Hits 14553 14555 +2
- Misses 2504 3096 +592
+ Partials 375 373 -2 ☔ View full report in Codecov by Sentry. |
/assign @skonto This should unblock your k8s bump |
9f09651
to
a8e7a70
Compare
/retest |
@dprotaso hi, could you update the PR? |
Keeping the fork up to date is not really tenable and it's fairly complex. We now simply manipulate the resulting CRD yaml after generation
works as expected generating the new field in all related resource files:
generates the expected output:
Should we add tests in case we need to fix something, instead of doing it manually? |
log.Fatalln("failed to read CRD directory", err) | ||
} | ||
|
||
for _, file := range files { |
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.
Although it is fast already could this be done concurrently? 🤔
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.
I don't think it's worth the complexity this would introduce - eg. right now I just log.Fatalf
which quits the program.
Doing it concurrently would require changing it to return errors etc.
/retest |
kourier-tls failure /retest |
again kourier-tls |
} | ||
|
||
func applyOverrideEntry(node *yaml.Node, entry entry) { | ||
for _, segment := range strings.Split(entry.path, ".") { |
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.
I guess there is no way to quickly reference a path (its node) so we have to iterate.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, skonto 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 |
Keeping the fork up to date is not really tenable and it's fairly complex. We now simply manipulate the resulting CRD yaml after generation