Skip to content

Commit 444b1dd

Browse files
authored
Update event sending docs
Align the docs to #368 changes
1 parent 3f209e4 commit 444b1dd

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

README.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -73,44 +73,44 @@ $ kn event build \
7373

7474
To send and event you should utilize `send` subcommand. The `send` command
7575
leverages the same builder-like interface as `build` command does. You could
76-
send an event to public address of your application by using `--to-url` option,
77-
or to supported in-cluster resources by using `--to` option.
76+
send an event to public address of your application or to supported
77+
in-cluster resources by using `--to` option.
7878

7979
#### Sending to public address
8080

81-
To send event to public address you use `--to-url` option:
81+
To send event to public address you use pass it to the `--to` option:
8282

8383
```sh
8484
$ kn event send \
8585
--field player.id=6354aa60-ddb1-452e-8c13-24893667de20 \
8686
--field player.game=2345 \
8787
--field points=456 \
8888
--type org.example.gaming.foo \
89-
--to-url http://ce-api.foo.example.org/
89+
--to http://ce-api.foo.example.org/
9090
```
9191

92-
> **NOTE**: All argument, except `--to-url` are optional. Use
92+
> **NOTE**: All argument, except `--to` are optional. Use
9393
> `kn event send --help` to see full usage information.
9494
9595
#### Sending to in-cluster resources
9696

97-
Sending event to in-cluster resources is done with a companion Job that is
98-
deployed on your cluster. In that way `kn-event` and send your event even to
97+
Sending events to in-cluster resources is done with a companion *Job* that
98+
is deployed on your cluster. This allows `kn-event` to send your events to
9999
resources that are not publicly accessible.
100100

101-
Send an event to a Knative service `event-display` in namespace `default`:
101+
Send an event to a Knative service `showcase` in current namespace:
102102

103103
```sh
104104
$ kn event send \
105105
--type org.example.kn.ping \
106106
--id $(uuidgen) \
107107
--field event.type=test \
108108
--field event.data=98765 \
109-
--to Service:serving.knative.dev/v1:event-display
109+
--to showcase
110110
```
111111

112-
> **NOTE**: All argument, except `--to-url` are optional. Use
113-
> `kn event send --help` to see full usage information.
112+
> **NOTE**: The --to option follow [the Kn sink format](https://github.com/knative/client/blob/main/docs/cmd/kn_trigger_create.md#options).
113+
> Use `kn event send --help` to see full format description.
114114
115115
## Install
116116

0 commit comments

Comments
 (0)