mirror of https://github.com/knative/docs.git
Eventing sanity pt2 (#3750)
* fix bash no copy added to terminal output * fix repeated phrase on receive adapter example md * fix contributors broken link
This commit is contained in:
Gabriel Freites
GitHub
parent
cc72b24942
commit
1a78f8a970
|
|
@ -58,7 +58,7 @@ You can create a broker by using the `kn` CLI or by applying YAML files using `k
|
|||
|
||||
This shows information about your broker. If the broker is working correctly, it shows a `READY` status of `True`:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
NAME READY REASON URL AGE
|
||||
default True http://broker-ingress.knative-eventing.svc.cluster.local/event-example/default 1m
|
||||
```
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ by entering the following command:
|
|||
|
||||
Example output:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
eventing-controller 1/1 1 1 10s
|
||||
eventing-webhook 1/1 1 1 9s
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ kubectl --namespace knative-debug get events
|
|||
|
||||
This should produce output along the lines of:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
LAST SEEN FIRST SEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
|
||||
20s 20s 1 to-be-deleted.157aadb9f376fc4e Pod Normal Scheduled default-scheduler Successfully assigned knative-debug/to-be-deleted to gke-kn24-default-pool-c12ac83b-pjf2
|
||||
```
|
||||
|
|
@ -348,7 +348,7 @@ kubectl --namespace knative-eventing logs -l messaging.knative.dev/channel=in-me
|
|||
|
||||
Ideally we will see lines like:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
{"level":"info","ts":"2019-08-16T13:50:55.424Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_receiver.go:147","msg":"Request mapped to channel: knative-debug/chan-kn-channel","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
{"level":"info","ts":"2019-08-16T13:50:55.425Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_dispatcher.go:112","msg":"Dispatching message to http://svc.knative-debug.svc.cluster.local/","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
{"level":"info","ts":"2019-08-16T13:50:55.981Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_receiver.go:140","msg":"Received request for chan-kn-channel.knative-debug.svc.cluster.local","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
|
|
@ -363,7 +363,7 @@ However if we see something like:
|
|||
NOTE: This error has been produced by settings spec.ports[0].port to 8081
|
||||
kubectl patch -n knative-debug svc svc -p '{"spec":{"ports": [{"port": 8081, "targetPort":8080}]}}' --type='merge'
|
||||
-->
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
{"level":"info","ts":"2019-08-16T16:10:16.859Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_receiver.go:140","msg":"Received request for chan-kn-channel.knative-debug.svc.cluster.local","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
{"level":"info","ts":"2019-08-16T16:10:16.859Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_receiver.go:147","msg":"Request mapped to channel: knative-debug/chan-kn-channel","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
{"level":"info","ts":"2019-08-16T16:10:16.859Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_dispatcher.go:112","msg":"Dispatching message to http://svc.knative-debug.svc.cluster.local/","knative.dev/controller":"in-memory-channel-dispatcher"}
|
||||
|
|
|
|||
|
|
@ -327,7 +327,7 @@ back with another event.
|
|||
|
||||
You should see something similar to:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
Event received.
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
@ -441,7 +441,7 @@ mesh via the Broker and can be delivered to other services using a Trigger
|
|||
|
||||
You should see something similar to:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
|
|||
|
|
@ -230,7 +230,7 @@ Helloworld-python app logs the context and the msg of the above event, and repli
|
|||
kubectl --namespace knative-samples logs -l app=helloworld-python --tail=50
|
||||
```
|
||||
You should see something similar to:
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
Event received. Context: Context Attributes,
|
||||
specversion: 0.3
|
||||
type: dev.knative.samples.helloworld
|
||||
|
|
@ -332,7 +332,7 @@ The `helloworld-python` app replies with an event type `type= dev.knative.sample
|
|||
|
||||
Example output:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
|
|||
|
|
@ -195,7 +195,7 @@ see them in the subscriber.
|
|||
|
||||
You should see something along the similar to:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
{"ID":"481014114648052","Data":"eyJzb3VyY2VfaWQiOiJpb3QtY29yZSBkZW1vIiwiZXZlbnRfaWQiOiJlaWQtMzI3MjJiMzItZWU5Mi00YzZlLWEzOTgtNDlmYjRkYWYyNGE1IiwiZXZlbnRfdHMiOjE1NTM3MTczOTYsIm1ldHJpYyI6MC4xMzY1MjI5OH0=","Attributes":{"deviceId":"iot-demo-client","deviceNumId":"2754785852315736","deviceRegistryId":"iot-demo","deviceRegistryLocation":"us-central1","projectId":"s9-demo","subFolder":""},"PublishTime":"2019-03-27T20:09:56.685Z"}
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ You must have a Kubernetes cluster with [Knative Eventing installed](../../../ad
|
|||
|
||||
Example output:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
eventing-controller 1/1 1 1 10s
|
||||
eventing-webhook 1/1 1 1 9s
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@ Before you can create an API server source, you must install Knative Eventing an
|
|||
|
||||
Example log output:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
☁️ cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ aliases:
|
|||
# Receive Adapter Implementation and Design
|
||||
|
||||
## Receive Adapter cmd
|
||||
Similar to the controller, we'll need an injection based `main.go` similar to the controller under `cmd/receiver_adapter/main.go`
|
||||
Similar to the controller, we'll need an injection based `main.go` under `cmd/receiver_adapter/main.go`
|
||||
```go
|
||||
// This Adapter generates events at a regular interval.
|
||||
package main
|
||||
|
|
|
|||
|
|
@ -163,7 +163,7 @@ entering the following command:
|
|||
|
||||
This returns the `Attributes` and `Data` of the events that the PingSource sent to the `event-display` service:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
☁️ cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
@ -181,7 +181,7 @@ entering the following command:
|
|||
|
||||
If you created a PingSource that sends binary data, you will also see output similar to the following:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
☁️ cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
|
|||
|
|
@ -266,7 +266,7 @@ service logs for your sink:
|
|||
2. From the output, observe the lines showing the request headers and body of the event message,
|
||||
sent by the source to the display function. For example:
|
||||
|
||||
```bash
|
||||
```{ .bash .no-copy }
|
||||
☁️ cloudevents.Event
|
||||
Validation: valid
|
||||
Context Attributes,
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@
|
|||
</div>
|
||||
<div>
|
||||
<h4>Contributions Welcome</h4>
|
||||
<a href="./contributing/" title="Contributing Link" class="md-button">Contribute</a>
|
||||
<a href="./help/contributor/" title="Contributing Link" class="md-button">Contribute</a>
|
||||
<p>Want to join the fun on Github? New users are always welcome!</p>
|
||||
</div>
|
||||
<div>
|
||||
|
|
|
|||
Loading…
Reference in New Issue