-
Notifications
You must be signed in to change notification settings - Fork 262
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 kn trigger list command to show correct v1/service sink output #1428
Conversation
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.
@Abirdcfly: 0 warnings.
In response to this:
Description
If the sink of the trigger is a normal service, the
kn trigger list
command will show it as ksvc, which is incorrectChanges
Reference
Fixes #
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.
Welcome @Abirdcfly! It looks like this is your first PR to knative/client 🎉 |
Hi @Abirdcfly. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/assign @RichieEscarez |
/ok-to-test |
"kind": "Service", | ||
"name": "foo", |
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.
Only kind and name are not enough here. An error will appear: "Unable to get the Subscriber's URI"
"kind": "Service", | ||
"name": "foo", |
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.
Only kind and name are not enough here. An error will appear: "Unable to get the Subscriber's URI"
looks like Group is not stabilized, more details here -> knative/eventing#5086. But if you include the version in the check, won't it need to be changed when a new knative serving version comes? |
Codecov Report
@@ Coverage Diff @@
## main #1428 +/- ##
=======================================
Coverage 78.70% 78.70%
=======================================
Files 162 162
Lines 8368 8368
=======================================
Hits 6586 6586
Misses 1098 1098
Partials 684 684
Continue to review full report at Codecov.
|
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.
everything looks good, one small suggestion.
Co-authored-by: Murugappan Chetty <itsmurugappan@gmail.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Abirdcfly, 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 |
Description
If the sink of the trigger is a normal service, the
kn trigger list
command will show it as ksvc, which is incorrectChanges
Reference
Fixes #