Skip to content
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(trigger): Make --filter flag truly optional #745

Merged
merged 3 commits into from
Mar 18, 2020

Conversation

dsimansk
Copy link
Contributor

Description

Fix issue with kn trigger create that always required --filter flag.

Changes

  • TriggerBuilder adds only empty Spec.Filter for empty or nil arrays
    • The above should also allow builder to be used to clean up existing filters
  • kn trigger describe doesn't print empty Filter

Reference

Fixes #744

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Mar 18, 2020
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dsimansk: 0 warnings.

In response to this:

Description

Fix issue with kn trigger create that always required --filter flag.

Changes

  • TriggerBuilder adds only empty Spec.Filter for empty or nil arrays
  • The above should also allow builder to be used to clean up existing filters
  • kn trigger describe doesn't print empty Filter

Reference

Fixes #744

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.

@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 18, 2020
@dsimansk
Copy link
Contributor Author

Does it make sense to omit filter in trigger describe command or rather add e.g. EMPTY or N/A?

Current change in this PR is omitting the filter:

➜  client git:(issue-744) ✗ kn trigger describe no-filter             
Name:         no-filter
Namespace:    default
Labels:       eventing.knative.dev/broker=default
Annotations:  eventing.knative.dev/creator=minikube-user, eventing.knative.dev/lastModifier=minik ...
Age:          28m
Broker:       default

Sink:         
  Name:       svc1
  Namespace:  
  Resource:   Service (serving.knative.dev/v1)

Conditions:  
  OK TYPE    AGE REASON

@knative-metrics-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-knative-client-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/eventing/v1alpha1/client.go 83.1% 83.9% 0.8
pkg/kn/commands/trigger/describe.go 83.3% 83.7% 0.3

@dsimansk
Copy link
Contributor Author

/test pull-knative-client-integration-tests

 ++ ./kn service create svc1 --no-wait --image gcr.io/knative-samples/helloworld-go -e TARGET=Knative -n kne2esmoketests
conversion webhook for &{map[apiVersion:serving.knative.dev/v1 kind:Service metadata:map[creationTimestamp:2020-03-18T11:23:20Z generation:1 name:svc1 namespace:kne2esmoketests uid:c14c3d36-c0ad-4dc9-a0dd-16a64a3d097c] spec:map[template:map[metadata:map[annotations:map[client.knative.dev/user-image:gcr.io/knative-samples/helloworld-go] creationTimestamp:<nil> name:svc1-qkwft-1] spec:map[containers:[map[env:[map[name:TARGET value:Knative]] image:gcr.io/knative-samples/helloworld-go name: resources:map[]]]]]]]} failed: Post https://webhook.knative-serving.svc:443/?timeout=30s: no endpoints available for service "webhook"
++ fail_test 

Copy link
Contributor

@rhuss rhuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, rhuss

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2020
@knative-prow-robot knative-prow-robot merged commit 58ee9c4 into knative:master Mar 18, 2020
dsimansk added a commit to dsimansk/client that referenced this pull request Mar 19, 2020
* fix(trigger): Make --filter flag truly optional

* fix(trigger): Update trigger docs

* chore: Update changelog
knative-prow-robot pushed a commit that referenced this pull request Mar 24, 2020
* fix(trigger): Make --filter flag truly optional (#745)

* fix(trigger): Make --filter flag truly optional

* fix(trigger): Update trigger docs

* chore: Update changelog

* fix(trigger): Fix filter delete for trigger update (#746)

* chore: Update changelog

* Fix plugin execution for Windows (#738)

Fixes #737

* Use exec.Command instend of syscall.Exec for windows.
* Fix a bug in plugin handler test when running it on windows.
* Fix typo.

* fix: Fix default config path on Windows (#752)

Co-authored-by: Lv Jiawei <lvjiawei@cmss.chinamobile.com>
@navidshaikh navidshaikh added the backport/pr A backport PR which is target to a release branch. label Apr 20, 2020
@rhuss rhuss added backported-to/0.13 and removed backport/pr A backport PR which is target to a release branch. labels Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kn trigger create fails without --filter flag
6 participants