From aa878027d277ed9fa21032835cb2d5a34aa0b03d Mon Sep 17 00:00:00 2001 From: sebgoa Date: Tue, 7 May 2019 17:53:40 +0200 Subject: [PATCH] address wrong manifest in gcppubsub sample (#1273) --- docs/eventing/samples/gcp-pubsub-source/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/eventing/samples/gcp-pubsub-source/README.md b/docs/eventing/samples/gcp-pubsub-source/README.md index a9bc1f34a..fea321ba0 100644 --- a/docs/eventing/samples/gcp-pubsub-source/README.md +++ b/docs/eventing/samples/gcp-pubsub-source/README.md @@ -76,9 +76,9 @@ source is most useful as a bridge from other GCP services, such as namespace `default`, feel free to change to any other namespace you would like to use instead: -```shell -kubectl label namespace default knative-eventing-injection=enabled -``` + ```shell + kubectl label namespace default knative-eventing-injection=enabled + ``` 1. Create a GCP PubSub Topic. If you change its name (`testing`), you also need to update the `topic` in the @@ -128,7 +128,7 @@ We will verify that the published message was sent into the Knative eventing system by looking at the logs of the function subscribed to the `pubsub-test` channel. -The function and the subscription were created by applying the `subscriber.yaml` +The function and the subscription were created by applying the [`trigger.yaml`](./trigger.yaml) manifest in the [deployment](#deployment) section above. 1. We need to wait for the downstream pods to get started and receive our event,