knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

address wrong manifest in gcppubsub sample (#1273)

This commit is contained in:
sebgoa 2019-05-07 17:53:40 +02:00 committed by Knative Prow Robot
parent 834b25a3cc
commit aa878027d2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/eventing/samples/gcp-pubsub-source/README.md
View File

@ -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 namespace `default`, feel free to change to any other namespace you would
like to use instead: like to use instead:
```shell ```shell
kubectl label namespace default knative-eventing-injection=enabled kubectl label namespace default knative-eventing-injection=enabled
``` ```
1. Create a GCP PubSub Topic. If you change its name (`testing`), you also need 1. Create a GCP PubSub Topic. If you change its name (`testing`), you also need
to update the `topic` in the 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` system by looking at the logs of the function subscribed to the `pubsub-test`
channel. 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. manifest in the [deployment](#deployment) section above.
1. We need to wait for the downstream pods to get started and receive our event, 1. We need to wait for the downstream pods to get started and receive our event,