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

Fix issue 3489 (update docs after tools move from eventing-contrib repo to eventing repo) (#3492) 

* checkpoint if I get the seds wrong

* remove cruft

* moar

* that should be it
This commit is contained in:
Ville Aikas 2021-04-27 12:37:53 -07:00 committed by GitHub
parent f304f2daa4
commit f166c16ead
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
46 changed files with 101 additions and 107 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/eventing/channels/channels.yaml
View File

@ -29,4 +29,4 @@ channels:
status: Proof of Concept
support: None
description: >
Kafka Channel implementation, contributed by SAP's Kyma project, is a Knative Eventing implementation of a Kafka backed channel which provides advanced functionality and production grade qualities as an alternative to what the eventing-contrib/kafka implementation offers.
Kafka Channel implementation, contributed by SAP's Kyma project, is a Knative Eventing implementation of a Kafka backed channel which provides advanced functionality and production grade qualities.

2
docs/eventing/debugging/example.yaml
View File

@ -95,7 +95,7 @@ spec:
spec:
containers:
- name: user-container
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
ports:
- containerPort: 8080

6
docs/eventing/getting-started.md
View File

@ -79,7 +79,7 @@ demonstrate how you can configure your event producers to target a specific cons
spec:
containers:
- name: event-display
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
@ -117,8 +117,8 @@ demonstrate how you can configure your event producers to target a specific cons
spec:
containers:
- name: event-display
# Source code: https://github.com/knative/eventing-contrib/tree/main/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
# Source code: https://github.com/knative/eventing/tree/main/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---

4
docs/eventing/samples/container-source/heartbeats-source.yaml
View File

@ -7,8 +7,8 @@ spec:
spec:
containers:
# This corresponds to a heartbeats image uri you build and publish,
# e.g. gcr.io/[gcloud-project]/knative.dev/eventing-contrib/cmd/heartbeats
- image: knative.dev/eventing-contrib/cmd/heartbeats
# e.g. gcr.io/[gcloud-project]/knative.dev/eventing/cmd/heartbeats
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/heartbeats
name: heartbeats
args:
- --period=1

12
docs/eventing/samples/container-source/index.md
View File

@ -20,17 +20,17 @@ creating your own event source as a ContainerSource.
### Prepare the heartbeats image
Knative [event-sources](https://github.com/knative/eventing-contrib) has a
Knative [event-sources](https://github.com/knative/eventing) has a
sample of heartbeats event source. You could clone the source code by
```
git clone -b "{{< branch >}}" https://github.com/knative/eventing-contrib.git
git clone -b "{{< branch >}}" https://github.com/knative/eventing.git
```
And then build a heartbeats image and publish to your image repo with
```
ko publish knative.dev/eventing-contrib/cmd/heartbeats
ko publish knative.dev/eventing/cmd/heartbeats
```
**Note**: `ko publish` requires:
@ -54,7 +54,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Use following command to create the service from `service.yaml`:
@ -131,7 +131,7 @@ Validation: valid
Context Attributes,
specversion: 1.0
type: dev.knative.eventing.samples.heartbeat
source: https://knative.dev/eventing-contrib/cmd/heartbeats/#event-test/mypod
source: https://knative.dev/eventing/cmd/heartbeats/#event-test/mypod
id: 2b72d7bf-c38f-4a98-a433-608fbcdd2596
time: 2019-10-18T15:23:20.809775386Z
contenttype: application/json
@ -167,7 +167,7 @@ any tools you like. Here are some basic guidelines:
[CloudEvents](https://github.com/cloudevents/spec/blob/master/spec.md#design-goals)
format is recommended.
[heartbeats](https://github.com/knative/eventing-contrib/blob/main/cmd/heartbeats/main.go)
[heartbeats](https://github.com/knative/eventing/blob/main/cmd/heartbeats/main.go)
event source is a sample for your reference.
### Create the ContainerSource using this container image

2
docs/eventing/samples/container-source/service.yaml
View File

@ -20,4 +20,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

2
docs/eventing/samples/github-source/index.md
View File

@ -32,7 +32,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Enter the following command to create the service from `service.yaml`:

2
docs/eventing/samples/github-source/service.yaml
View File

@ -7,4 +7,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

6
docs/eventing/samples/gitlab-source/index.md
View File

@ -26,11 +26,11 @@ You will need:
### Install GitLab Event Source
GitLab Event source lives in the [knative/eventing-contrib](https://github.com/knative/eventing-contrib). Head to the releases page, find the latest release with `gitlab.yaml`
GitLab Event source lives in the [knative-sandbox/eventing-gitlab](https://github.com/knative-sandbox/eventing-gitlab). Head to the releases page, find the latest release with `gitlab.yaml`
artifact and replace the `<RELEASE>` with version tag:
```shell
kubectl apply -f https://github.com/knative/eventing-contrib/releases/download/<RELEASE>/gitlab.yaml
kubectl apply -f https://github.com/knative-sandbox/eventing-gitlab/releases/download/<RELEASE>/gitlab.yaml
```
Check that the manager is running:
@ -71,7 +71,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Create the service:

4
docs/eventing/samples/helloworld/helloworld-go/_index.md
View File

@ -383,8 +383,8 @@ mesh via the Broker and can be delivered to other services using a Trigger
spec:
containers:
- name: helloworld-go
# Source code: https://github.com/knative/eventing-contrib/tree/main/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
# Source code: https://github.com/knative/eventing/tree/main/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
# Service that exposes event-display app.
# This will be the subscriber for the Trigger

2
docs/eventing/samples/helloworld/helloworld-python/_index.md
View File

@ -266,7 +266,7 @@ The `helloworld-python` app replies with an event type `type= dev.knative.sample
spec:
containers:
- name: helloworld-python
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
# Service that exposes event-display app.
# This will be the subscriber for the Trigger

2
docs/eventing/samples/iot-core/trigger.yaml
View File

@ -23,4 +23,4 @@ spec:
template:
spec:
containers:
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

2
docs/eventing/samples/kafka/binding/event-display.yaml
View File

@ -20,4 +20,4 @@
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

6
docs/eventing/samples/kafka/binding/index.md
View File

@ -42,7 +42,7 @@ via Kafka Source
1. (Optional) Source code for Event Display service
Get the source code of Event Display container image from
[here](https://github.com/knative/eventing-contrib/blob/main/cmd/event_display/main.go)
[here](https://github.com/knative/eventing/blob/main/cmd/event_display/main.go)
1. Deploy the Event Display Service via kubectl:
@ -55,7 +55,7 @@ via Kafka Source
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
```
@ -70,7 +70,7 @@ via Kafka Source
below
```
kn service create event-display --image=gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
kn service create event-display --image=gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
1. Ensure that the Service pod is running. The pod name will be prefixed with

2
docs/eventing/samples/kafka/channel/000-ksvc.yaml
View File

@ -6,4 +6,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

2
docs/eventing/samples/kafka/source/event-display.yaml
View File

@ -20,4 +20,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

4
docs/eventing/samples/kafka/source/index.md
View File

@ -75,8 +75,8 @@ Tutorial on how to build and deploy a `KafkaSource` [Eventing source](../../../s
spec:
containers:
- # This corresponds to
# https://github.com/knative/eventing-contrib/tree/main/cmd/event_display/main.go
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
# https://github.com/knative/eventing/tree/main/cmd/event_display/main.go
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
1. Deploy the Event Display Service

2
docs/eventing/samples/parallel/multiple-branches/_index.md
View File

@ -96,7 +96,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Change `default` below to create the `Sequence` in the Namespace where you want

2
docs/eventing/samples/parallel/multiple-branches/event-display.yaml
View File

@ -6,4 +6,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

2
docs/eventing/samples/parallel/mutual-exclusivity/_index.md
View File

@ -87,7 +87,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
```shell

2
docs/eventing/samples/parallel/mutual-exclusivity/event-display.yaml
View File

@ -6,4 +6,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

4
docs/eventing/samples/ping-source/index.md
View File

@ -34,7 +34,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
EOF
```
{{< /tab >}}
@ -43,7 +43,7 @@ EOF
Use following command to create the service using the kn cli:
```shell
kn service create event-display --image gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
kn service create event-display --image gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
{{< /tab >}}
{{< /tabs >}}

2
docs/eventing/samples/ping-source/service.yaml
View File

@ -8,4 +8,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

2
docs/eventing/samples/sequence/sequence-reply-to-event-display/event-display.yaml
View File

@ -6,4 +6,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

10
docs/eventing/samples/sequence/sequence-reply-to-event-display/index.md
View File

@ -12,7 +12,7 @@ taking the output of that `Sequence` and displaying the resulting output.
![Logical Configuration](./sequence-reply-to-event-display.png)
The functions used in these examples live in
[https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go](https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go).
[https://github.com/knative/eventing/blob/main/cmd/appender/main.go](https://github.com/knative/eventing/blob/main/cmd/appender/main.go).
## Prerequisites
@ -40,7 +40,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -54,7 +54,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -67,7 +67,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"
@ -132,7 +132,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Change `default` below to create the `Sequence` in the Namespace where you want

6
docs/eventing/samples/sequence/sequence-reply-to-event-display/steps.yaml
View File

@ -6,7 +6,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -20,7 +20,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -33,7 +33,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"

2
docs/eventing/samples/sequence/sequence-reply-to-sequence/event-display.yaml
View File

@ -6,4 +6,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

16
docs/eventing/samples/sequence/sequence-reply-to-sequence/index.md
View File

@ -13,7 +13,7 @@ finally displaying the resulting output.
![Logical Configuration](./sequence-reply-to-sequence.png)
The functions used in these examples live in
[https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go](https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go).
[https://github.com/knative/eventing/blob/main/cmd/appender/main.go](https://github.com/knative/eventing/blob/main/cmd/appender/main.go).
## Prerequisites
@ -41,7 +41,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -55,7 +55,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -68,7 +68,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"
@ -81,7 +81,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 3"
@ -95,7 +95,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 4"
@ -108,7 +108,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 5"
@ -212,7 +212,7 @@ spec:
template:
spec:
containerers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
Change `default` below to create the `Sequence` in the Namespace where you want

12
docs/eventing/samples/sequence/sequence-reply-to-sequence/steps.yaml
View File

@ -6,7 +6,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -20,7 +20,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -33,7 +33,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"
@ -47,7 +47,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 3"
@ -60,7 +60,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 4"
@ -73,7 +73,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 5"

8
docs/eventing/samples/sequence/sequence-terminal/index.md
View File

@ -13,7 +13,7 @@ events.
![Logical Configuration](./sequence-terminal.png)
The functions used in these examples live in
[https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go](https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go).
[https://github.com/knative/eventing/blob/main/cmd/appender/main.go](https://github.com/knative/eventing/blob/main/cmd/appender/main.go).
## Prerequisites
@ -40,7 +40,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -54,7 +54,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -67,7 +67,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"

6
docs/eventing/samples/sequence/sequence-terminal/steps.yaml
View File

@ -6,7 +6,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -20,7 +20,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -33,7 +33,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"

2
docs/eventing/samples/sequence/sequence-with-broker-trigger/display-trigger.yaml
View File

@ -6,7 +6,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
apiVersion: eventing.knative.dev/v1
kind: Trigger

10
docs/eventing/samples/sequence/sequence-with-broker-trigger/index.md
View File

@ -24,7 +24,7 @@ If you want to use different type of `Channel`, you will have to modify the
![Logical Configuration](./sequence-with-broker-trigger.png)
The functions used in these examples live in
[https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go](https://github.com/knative/eventing-contrib/blob/main/cmd/appender/main.go).
[https://github.com/knative/eventing/blob/main/cmd/appender/main.go](https://github.com/knative/eventing/blob/main/cmd/appender/main.go).
## Setup
@ -52,7 +52,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -66,7 +66,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -79,7 +79,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"
@ -206,7 +206,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
---
apiVersion: eventing.knative.dev/v1
kind: Trigger

6
docs/eventing/samples/sequence/sequence-with-broker-trigger/steps.yaml
View File

@ -6,7 +6,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 0"
@ -20,7 +20,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 1"
@ -33,7 +33,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Handled by 2"

4
docs/eventing/sources/_index.md
View File

@ -42,11 +42,11 @@ kn source list
| [Container Source](./containersource.md) | v1 | Knative | The ContainerSource will instantiate container image(s) that can generate events until the ContainerSource is deleted. This may be used, for example, to poll an FTP server for new files or generate events at a set time interval. Given a `spec.template` with at least a container image specified, ContainerSource will keep a `Pod` running with the specified image(s). `K_SINK` (destination address) and `KE_CE_OVERRIDES` (JSON CloudEvents attributes) environment variables are injected into the running image(s). It is used by multiple other Sources as underlying infrastructure. Refer to the [Container Source](../samples/container-source) example for more details. |
| [GitHub](../samples/github-source) | v1alpha1 | Knative | Registers for events of the specified types on the specified GitHub organization or repository, and brings those events into Knative. The GitHubSource fires a new event for selected [GitHub event types](https://developer.github.com/v3/activity/events/types/). See the [GitHub Source](../samples/github-source) example for more details. |
| [GitLab](../samples/gitlab-source) | v1alpha1 | Knative | Registers for events of the specified types on the specified GitLab repository, and brings those events into Knative. The GitLabSource creates a webhooks for specified [event types](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#events), listens for incoming events, and passes them to a consumer. See the [GitLab Source](../samples/gitlab-source) example for more details. |
| [Heartbeats](https://github.com/knative/eventing-contrib/tree/main/cmd/heartbeats) | N/A | Knative | Uses an in-memory timer to produce events at the specified interval. |
| [Heartbeats](https://github.com/knative/eventing/tree/main/cmd/heartbeats) | N/A | Knative | Uses an in-memory timer to produce events at the specified interval. |
| [PingSource](./pingsource) | v1beta2 | Knative | Produces events with a fixed payload on a specified [Cron](https://en.wikipedia.org/wiki/Cron) schedule. See the [Ping Source](../samples/ping-source) example for more details. |
| [RabbitMQ](https://github.com/knative-sandbox/eventing-rabbitmq) | Active development | None | Brings [RabbitMQ](https://www.rabbitmq.com/) messages into Knative.
| [SinkBinding](./sinkbinding/) | v1 | Knative | The SinkBinding can be used to author new event sources using any of the familiar compute abstractions that Kubernetes makes available (e.g. Deployment, Job, DaemonSet, StatefulSet), or Knative abstractions (e.g. Service, Configuration). SinkBinding provides a framework for injecting `K_SINK` (destination address) and `K_CE_OVERRIDES` (JSON cloudevents attributes) environment variables into any Kubernetes resource which has a `spec.template` that looks like a Pod (aka PodSpecable). See the [SinkBinding](../samples/container-source) example for more details. |
| [WebSocket](https://github.com/knative/eventing-contrib/tree/main/cmd/websocketsource) | N/A | Knative | Opens a WebSocket to the specified source and packages each received message as a Knative event. |
| [WebSocket](https://github.com/knative/eventing/tree/main/cmd/websocketsource) | N/A | Knative | Opens a WebSocket to the specified source and packages each received message as a Knative event. |
## Third-Party Sources

2
docs/eventing/sources/apache-camel-source/display_resources.yaml
View File

@ -36,4 +36,4 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display

12
docs/eventing/sources/containersource.md
View File

@ -29,17 +29,17 @@ The ContainerSource source type is enabled by default when you install Knative E
This example shows how the heartbeats container sends events to the Event Display Service.
### Preparing the heartbeats image
Knative [event-sources](https://github.com/knative/eventing-contrib) has a
Knative [event-sources](https://github.com/knative/eventing) has a
sample of heartbeats event source. You could clone the source code by
```
git clone -b "{{< branch >}}" https://github.com/knative/eventing-contrib.git
git clone -b "{{< branch >}}" https://github.com/knative/eventing.git
```
And then build a heartbeats image and publish to your image repo with
```
ko publish knative.dev/eventing-contrib/cmd/heartbeats
ko publish ko://knative.dev/eventing/cmd/heartbeats
```
### Creating a namespace
@ -72,7 +72,7 @@ spec:
spec:
containers:
- name: event-display
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
@ -111,7 +111,7 @@ spec:
spec:
containers:
# This corresponds to a heartbeats image uri you build and publish in the previous step
# e.g. gcr.io/[gcloud-project]/knative.dev/eventing-contrib/cmd/heartbeats
# e.g. gcr.io/[gcloud-project]/knative.dev/eventing/cmd/heartbeats
- image: <heartbeats_image_uri>
name: heartbeats
args:
@ -146,7 +146,7 @@ Validation: valid
Context Attributes,
specversion: 1.0
type: dev.knative.eventing.samples.heartbeat
source: https://knative.dev/eventing-contrib/cmd/heartbeats/#event-test/mypod
source: https://knative.dev/eventing/cmd/heartbeats/#event-test/mypod
id: 2b72d7bf-c38f-4a98-a433-608fbcdd2596
time: 2019-10-18T15:23:20.809775386Z
contenttype: application/json

2
docs/eventing/sources/creating-event-sources/writing-event-source/06-yaml.md
View File

@ -42,7 +42,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---
apiVersion: samples.knative.dev/v1alpha1
kind: SampleSource

2
docs/eventing/sources/pingsource.md
View File

@ -51,7 +51,7 @@ spec:
spec:
containers:
- name: event-display
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
---

14
docs/eventing/sources/sinkbinding.md
View File

@ -52,7 +52,7 @@ Create a Knative service:
{{% tab name="kn" %}}
```bash
kn service create hello --image gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display --env RESPONSE="Hello Serverless!"
kn service create hello --image gcr.io/knative-releases/knative.dev/eventing/cmd/event_display --env RESPONSE="Hello Serverless!"
```
{{< /tab >}}
@ -68,7 +68,7 @@ kn service create hello --image gcr.io/knative-releases/knative.dev/eventing-con
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
```
2. Apply the file:
```bash
@ -104,7 +104,7 @@ Create a `CronJob` object:
restartPolicy: Never
containers:
- name: single-heartbeat
image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/heartbeats
image: gcr.io/knative-releases/knative.dev/eventing/cmd/heartbeats
args:
- --period=1
env:
@ -126,7 +126,7 @@ Create a `CronJob` object:
#### Cloning a sample heartbeat cron job
Knative [event-contrib](https://github.com/knative/eventing-contrib) contains a
Knative [event-contrib](https://github.com/knative/eventing) contains a
sample heartbeats event source.
##### Prerequisites
@ -140,11 +140,11 @@ sample heartbeats event source.
1. Clone the `event-contib` repository:
```bash
$ git clone -b "{{< branch >}}" https://github.com/knative/eventing-contrib.git
$ git clone -b "{{< branch >}}" https://github.com/knative/eventing.git
```
2. Build a heartbeats image, and publish the image to your image repository:
```bash
$ ko publish knative.dev/eventing-contrib/cmd/heartbeats
$ ko publish knative.dev/eventing/cmd/heartbeats
```
<!-- TODO: Add tabs if there are kn commands etc to do this also-->
@ -215,7 +215,7 @@ kn source binding create bind-heartbeat \
Context Attributes,
specversion: 1.0
type: dev.knative.eventing.samples.heartbeat
source: https://knative.dev/eventing-contrib/cmd/heartbeats/#default/heartbeat-cron-1582120020-75qrz
source: https://knative.dev/eventing/cmd/heartbeats/#default/heartbeat-cron-1582120020-75qrz
id: 5f4122be-ac6f-4349-a94f-4bfc6eb3f687
time: 2020-02-19T13:47:10.41428688Z
datacontenttype: application/json

1
docs/install/upgrade-installation.md
View File

@ -28,7 +28,6 @@ applications:
- [Serving](https://github.com/knative/serving/releases)
- [Eventing](https://github.com/knative/eventing/releases)
- [Eventing-Contrib](https://github.com/knative/eventing-contrib/releases)
Release notes are published with each version on the "Releases" page of their
respective repositories in GitHub.

5
hack/gen-api-reference-docs.sh
View File

@ -35,11 +35,6 @@ KNATIVE_EVENTING_IMPORT_PATH="knative.dev/eventing"
KNATIVE_EVENTING_COMMIT="${KNATIVE_EVENTING_COMMIT:?specify the \$KNATIVE_EVENTING_COMMIT variable}"
KNATIVE_EVENTING_OUT_FILE="eventing/eventing.md"
# KNATIVE_EVENTING_CONTRIB_REPO="github.com/knative/eventing-contrib"
# KNATIVE_EVENTING_CONTRIB_IMPORT_PATH="knative.dev/eventing-contrib"
# KNATIVE_EVENTING_CONTRIB_COMMIT="${KNATIVE_EVENTING_CONTRIB_COMMIT:?specify the \$KNATIVE_EVENTING_CONTRIB_COMMIT variable}"
# KNATIVE_EVENTING_CONTRIB_OUT_FILE="eventing/eventing-contrib.md"
cleanup_refdocs_root=
cleanup_repo_clone_root=
trap cleanup EXIT

2
tutorials/katacoda/3-eventing-intro-channels/step2.md
View File

@ -18,7 +18,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
EOF
```{{execute}}

2
tutorials/katacoda/3-eventing-intro-channels/step3.md
View File

@ -53,7 +53,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
EOF
done
```{{execute}}

4
tutorials/katacoda/3-eventing-intro-channels/step4.md
View File

@ -23,7 +23,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
EOF
```{{execute}}
@ -39,7 +39,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/appender
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
env:
- name: MESSAGE
value: " - Updating this message a little..."

2
tutorials/katacoda/4-eventing-intro-broker/step2.md
View File

@ -46,7 +46,7 @@ spec:
template:
spec:
containers:
- image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display
- image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
EOF
done
```{{execute}}