You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/eventing/samples/helloworld/helloworld-python/README.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,7 @@ folder) you're ready to build and deploy the sample app.
159
159
docker push {username}/helloworld-python
160
160
```
161
161
162
-
1. After the build has completed and the container is pushed to docker hub, you
162
+
1. After the build has completed and the container is pushed to Docker Hub, you
163
163
can deploy the sample application into your cluster. Ensure that the container image value
164
164
in `sample-app.yaml` matches the container you built in the previous step. Apply
165
165
the configuration using `kubectl`:
@@ -181,11 +181,10 @@ folder) you're ready to build and deploy the sample app.
181
181
kubectl --namespace knative-samples get trigger helloworld-python
182
182
```
183
183
## Send and verify CloudEvents
184
-
Once you have deployed the application and verified that the namespace, sample application and trigger are ready, let's send a CloudEvent.
184
+
After you have deployed the application, and have verified that the namespace, sample application and trigger are ready, you can send a CloudEvent.
185
185
186
186
### Send CloudEvent to the Broker
187
-
188
-
We can send an http request directly to the Broker with correct CloudEvent headers set.
187
+
You can send an HTTP request directly to the Knative [broker](../../../broker-trigger.md) if the correct CloudEvent headers are set.
189
188
190
189
1. Deploy a curl pod and SSH into it
191
190
```shell
@@ -235,10 +234,10 @@ Helloworld-python app logs the context and the msg of the above event, and repli
235
234
{"msg":"Hi from Knative!"}
236
235
237
236
```
238
-
Play around with the CloudEvent attributes in the curl command and the trigger specification to understand how Triggers work.
237
+
Try the CloudEvent attributes in the curl command and the trigger specification to understand how [triggers](../../../broker-trigger.md#trigger) work.
239
238
240
239
## Verify reply from helloworld-python app
241
-
`helloworld-python` app replies back with an event of `type= dev.knative.samples.hifromknative`, and `source=knative/eventing/samples/hello-world`. This event enters the eventing mesh via the Broker and can be delivered to other services using a Trigger
240
+
The `helloworld-python` app replies with an event type`type= dev.knative.samples.hifromknative`, and source`source=knative/eventing/samples/hello-world`. The event enters the eventing mesh through the broker, and can be delivered to event sinks using a trigger
242
241
243
242
1. Deploy a pod that receives any CloudEvent and logs the event to its output.
0 commit comments