diff --git a/docs/eventing/samples/cronjob-source/README.md b/docs/eventing/samples/cronjob-source/README.md index cf90bebf33d..956578729c3 100644 --- a/docs/eventing/samples/cronjob-source/README.md +++ b/docs/eventing/samples/cronjob-source/README.md @@ -17,14 +17,14 @@ Service that dumps incoming messages to its log. apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: message-dumper + name: event-display spec: runLatest: configuration: revisionTemplate: spec: container: - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display ``` Use following command to create the service from `service.yaml`: @@ -51,7 +51,7 @@ spec: sink: apiVersion: serving.knative.dev/v1alpha1 kind: Service - name: message-dumper + name: event-display ``` Use following command to create the event source from `cronjob-source.yaml`: @@ -66,14 +66,14 @@ We will verify that the message was sent to the Knative eventing system by looking at message dumper logs. ```shell -kubectl logs -l serving.knative.dev/service=message-dumper -c user-container --since=10m +kubectl logs -l serving.knative.dev/service=event-display -c user-container --since=10m ``` You should see log lines showing the request headers and body from the source: ``` 2019/03/14 14:28:06 Message Dumper received a message: POST / HTTP/1.1 -Host: message-dumper.default.svc.cluster.local +Host: event-display.default.svc.cluster.local Transfer-Encoding: chunked Accept-Encoding: gzip Ce-Cloudeventsversion: 0.1 @@ -90,7 +90,7 @@ You can also use [`kail`](https://github.com/boz/kail) instead of `kubectl logs` to tail the logs of the subscriber. ```shell -kail -l serving.knative.dev/service=message-dumper -c user-container --since=10m +kail -l serving.knative.dev/service=event-display -c user-container --since=10m ``` ### Cleanup diff --git a/docs/eventing/samples/cronjob-source/service.yaml b/docs/eventing/samples/cronjob-source/service.yaml index a61c6cd1340..a4ee4eedd58 100644 --- a/docs/eventing/samples/cronjob-source/service.yaml +++ b/docs/eventing/samples/cronjob-source/service.yaml @@ -3,11 +3,11 @@ apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: message-dumper + name: event-display spec: runLatest: configuration: revisionTemplate: spec: container: - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display diff --git a/docs/eventing/samples/gcp-pubsub-source/README.md b/docs/eventing/samples/gcp-pubsub-source/README.md index d01be06ccc7..478dedb9a85 100644 --- a/docs/eventing/samples/gcp-pubsub-source/README.md +++ b/docs/eventing/samples/gcp-pubsub-source/README.md @@ -132,7 +132,7 @@ not, then you will need to look downstream yourself. - You can check the status of the downstream pods with: ```shell - kubectl get pods --selector serving.knative.dev/service=message-dumper + kubectl get pods --selector serving.knative.dev/service=event-display ``` You should see at least one. @@ -140,7 +140,7 @@ not, then you will need to look downstream yourself. 1. Inspect the logs of the subscriber: ```shell - kubectl logs --selector serving.knative.dev/service=message-dumper -c user-container + kubectl logs --selector serving.knative.dev/service=event-display -c user-container ``` You should see log lines similar to: diff --git a/docs/eventing/samples/gcp-pubsub-source/trigger.yaml b/docs/eventing/samples/gcp-pubsub-source/trigger.yaml index 688b02297fd..1ec2381414f 100644 --- a/docs/eventing/samples/gcp-pubsub-source/trigger.yaml +++ b/docs/eventing/samples/gcp-pubsub-source/trigger.yaml @@ -3,7 +3,7 @@ apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: message-dumper + name: event-display spec: runLatest: configuration: @@ -11,8 +11,8 @@ spec: spec: container: # This corresponds to - # https://github.com/knative/eventing-sources/blob/release-0.3/cmd/message_dumper/dumper.go - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper@sha256:8423232db7a7b4010c0cfbfaef95745efe962631af9b7456903825801a7893f7 + # https://github.com/knative/eventing-sources/blob/release-0.5/cmd/event_display/main.go + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display@sha256:bf45b3eb1e7fc4cb63d6a5a6416cf696295484a7662e0cf9ccdf5c080542c21d --- @@ -28,5 +28,5 @@ spec: ref: apiVersion: serving.knative.dev/v1alpha1 kind: Service - name: message-dumper + name: event-display diff --git a/docs/eventing/samples/github-source/README.md b/docs/eventing/samples/github-source/README.md index 700c05867e8..72ef14463a6 100644 --- a/docs/eventing/samples/github-source/README.md +++ b/docs/eventing/samples/github-source/README.md @@ -30,14 +30,14 @@ defines this basic service. apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: github-message-dumper + name: github-event-display spec: runLatest: configuration: revisionTemplate: spec: container: - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display ``` Enter the following command to create the service from `service.yaml`: @@ -122,7 +122,7 @@ spec: sink: apiVersion: serving.knative.dev/v1alpha1 kind: Service - name: github-message-dumper + name: github-event-display ``` Then, apply that yaml using `kubectl`: @@ -148,14 +148,14 @@ by looking at our message dumper function logs. ```shell kubectl --namespace default get pods -kubectl --namespace default logs github-message-dumper-XXXX user-container +kubectl --namespace default logs github-event-display-XXXX user-container ``` You should log lines similar to: ``` 2018/11/08 18:25:34 Message Dumper received a message: POST / HTTP/1.1 -Host: github-message-dumper.knative-demo.svc.cluster.local +Host: github-event-display.knative-demo.svc.cluster.local Accept-Encoding: gzip Ce-Cloudeventsversion: 0.1 Ce-Eventid: a8d4cf20-e383-11e8-8069-46e3c8ad2b4d diff --git a/docs/eventing/samples/github-source/service.yaml b/docs/eventing/samples/github-source/service.yaml index 36cd73c1aa9..2a220a3538f 100644 --- a/docs/eventing/samples/github-source/service.yaml +++ b/docs/eventing/samples/github-source/service.yaml @@ -9,4 +9,4 @@ spec: revisionTemplate: spec: container: - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display diff --git a/docs/eventing/samples/iot-core/README.md b/docs/eventing/samples/iot-core/README.md index 5e7b3dfd05b..041e89c0924 100644 --- a/docs/eventing/samples/iot-core/README.md +++ b/docs/eventing/samples/iot-core/README.md @@ -176,7 +176,7 @@ see them in the subscriber. 1. Inspect the logs of the subscriber: ```shell - kubectl logs --selector serving.knative.dev/service=message-dumper -c user-container + kubectl logs --selector serving.knative.dev/service=event-display -c user-container ``` You should see something along the similar to: diff --git a/docs/eventing/samples/iot-core/trigger.yaml b/docs/eventing/samples/iot-core/trigger.yaml index c55debc7bf8..d14a3365cb0 100644 --- a/docs/eventing/samples/iot-core/trigger.yaml +++ b/docs/eventing/samples/iot-core/trigger.yaml @@ -8,7 +8,7 @@ spec: ref: apiVersion: serving.knative.dev/v1alpha1 kind: Service - name: message-dumper + name: event-display --- # This is a very simple Knative Service that writes the input request to its log. @@ -16,7 +16,7 @@ spec: apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: message-dumper + name: event-display namespace: default spec: runLatest: @@ -25,5 +25,5 @@ spec: spec: container: # This corresponds to - # https://github.com/knative/eventing-sources/blob/release-0.3/cmd/message_dumper/dumper.go - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper@sha256:8423232db7a7b4010c0cfbfaef95745efe962631af9b7456903825801a7893f7 + # https://github.com/knative/eventing-sources/blob/release-0.5/cmd/event_display/main.go + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display@sha256:bf45b3eb1e7fc4cb63d6a5a6416cf696295484a7662e0cf9ccdf5c080542c21d diff --git a/docs/eventing/samples/kubernetes-event-source/README.md b/docs/eventing/samples/kubernetes-event-source/README.md index 9d3ea2490f6..e451ac721ba 100644 --- a/docs/eventing/samples/kubernetes-event-source/README.md +++ b/docs/eventing/samples/kubernetes-event-source/README.md @@ -73,7 +73,7 @@ will need to look downstream yourself. ```shell kubectl get pods -kubectl logs -l serving.knative.dev/service=message-dumper -c user-container +kubectl logs -l serving.knative.dev/service=event-display -c user-container ``` You should see log lines similar to: diff --git a/docs/eventing/samples/kubernetes-event-source/trigger.yaml b/docs/eventing/samples/kubernetes-event-source/trigger.yaml index cfcf062faf6..2e7467d5087 100644 --- a/docs/eventing/samples/kubernetes-event-source/trigger.yaml +++ b/docs/eventing/samples/kubernetes-event-source/trigger.yaml @@ -8,7 +8,7 @@ spec: ref: apiVersion: serving.knative.dev/v1alpha1 kind: Service - name: message-dumper + name: event-display --- # This is a very simple Knative Service that writes the input request to its log. @@ -16,7 +16,7 @@ spec: apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: - name: message-dumper + name: event-display namespace: default spec: runLatest: @@ -25,5 +25,5 @@ spec: spec: container: # This corresponds to - # https://github.com/knative/eventing-sources/blob/release-0.3/cmd/message_dumper/dumper.go - image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/message_dumper@sha256:8423232db7a7b4010c0cfbfaef95745efe962631af9b7456903825801a7893f7 + # https://github.com/knative/eventing-sources/blob/release-0.5/cmd/event_display/main.go + image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display@sha256:bf45b3eb1e7fc4cb63d6a5a6416cf696295484a7662e0cf9ccdf5c080542c21d