-
Notifications
You must be signed in to change notification settings - Fork 261
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
Add support for Eventing/v1beta2 EventTypes #1829
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dsimansk 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 |
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.
@dsimansk: 1 warning.
In response to this:
Description
Changes
- 🎁 New Add support for Eventing/v1beta2 EventTypes
Reference
Fixes #1818
Release Note
Add support for Eventing/v1beta2 EventTypes
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@@ -25,6 +25,6 @@ type EventtypeFlags struct { | |||
func (e *EventtypeFlags) Add(cmd *cobra.Command) { | |||
cmd.Flags().StringVarP(&e.Type, "type", "t", "", "Cloud Event type") | |||
cmd.Flags().StringVar(&e.Source, "source", "", "Cloud Event source") | |||
cmd.Flags().StringVarP(&e.Broker, "broker", "b", "", "Cloud Event broker") | |||
cmd.Flags().StringVarP(&e.Broker, "broker", "b", "", "Cloud Event Broker. This flag is added for the convenience, since Eventing v1beta2 brokers as represented as KReference type.") |
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 clarification is more confusing than it helps. I don't think that the user know ad hoc what a "KReference type" is. For the help message it would be better to use something like "Deprecated. Please use --reference instead", or if its not deprecated, I just would keep it as is. Anything else is just confusing,.
pkg/kn/commands/eventtype/create.go
Outdated
"You can specify a broker, channel, or fully qualified GVK resource. " + | ||
"Examples: '" + flag + " broker:nest' for a broker 'nest', " + | ||
"'" + flag + " channel:pipe' for a channel 'pipe'." | ||
//TODO: craft fqdn GVK example. |
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.
Important to not forget it here, since using a GVK is the most complex way to specify this reference so there should be an example for sure.
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.
From my e2e tests it seems there's an issue with GVK. At least it's not working for EventTypes
. I'll be certainly taking a bit in-depth look. I'd say we have a bug there. :)
Looks straightforward to me. I've added some comments to the wording. I wonder whether we should make |
I'd prefer to keep it untouched. Even deprecating will take time to remove it completely, but for the sake of convenience it's still handy for most common use case. |
"'" + flag + " special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. " + | ||
"GroupVersionResource requires resource name in a lower case plural form. The inputs are sanitized on best effort basis, " + | ||
"but in case of 'resource not found' error it may help to double check and correct the input. " + |
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.
@rhuss that's the case size is a culprit of my initial "bug" hunch. Can you please take a look at wording since you're master writer please?
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1829 +/- ##
==========================================
- Coverage 79.73% 79.67% -0.06%
==========================================
Files 179 179
Lines 13898 13952 +54
==========================================
+ Hits 11081 11116 +35
- Misses 2054 2069 +15
- Partials 763 767 +4
☔ View full report in Codecov by Sentry. |
/test all |
/retest |
11008d1
to
d6d5617
Compare
@dsimansk: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
It seems very strange that |
/close |
@dsimansk: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description
Changes
Reference
Fixes #1818
/cc @matzew @rhuss
Release Note