-
Notifications
You must be signed in to change notification settings - Fork 600
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
kubectl explain for Trigger #3845
Conversation
this is ready for review, fyi @lionelvillard |
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 doing this!
@@ -55,22 +55,22 @@ spec: | |||
properties: | |||
broker: | |||
type: string | |||
description: "Broker that this trigger receives events from. If not specified, will default to 'default'." |
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.
" If not specified, will default to 'default'.", isn't it valid anymore?
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 removed this following changes from #3573 (which I forgot to mention this PR supersedes). Let me know if you think I should add it back.
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 think this defaulting behavior exists and we should mention it in the description. Also, I see that Ville there leaves this https://github.com/knative/eventing/pull/3573/files#diff-35c872630bcc973ea91f0d72122bb2f7R60 untouched, and removes that from the trigger_types.go
, but I'm not sure why.
WDYT?
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.
the default behavior exists in v1beta1, not v1. I would add it just in the v1beta1 schema.
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.
Yeah, only v1beta1
.
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.
added it here for v1beta1 schema.
/approve |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lionelvillard, nlopezgi, pierDipi 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 |
addressed comments. Should be ready to go in once tests pass. Thanks for the reviews and clarifications @pierDipi @lionelvillard |
/retest |
/retest |
ugh, forgot to fix some single quotes, lets see if tests pass now. |
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-eventing-conformance-tests:
|
/test pull-knative-eventing-conformance-tests |
@lionelvillard this needs a renewed lgtm. Thanks |
/lgtm |
Part of #3054
Proposed Changes
kubectl explain
#3054