This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k-examples.git
commit 8aebb4715d0b89c257b1193fc490b489040b160b
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Jul 14 11:50:43 2020 +0200
AWS Kinesis source basic example: Should point to 0.15.0 Knative
documentation, with 0.16.0, the latest, the spec has been changed pointing to
some v1
---
04-aws-kinesis-source-basic/readme.didact.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/04-aws-kinesis-source-basic/readme.didact.md
b/04-aws-kinesis-source-basic/readme.didact.md
index 1970ab4..3068c45 100644
--- a/04-aws-kinesis-source-basic/readme.didact.md
+++ b/04-aws-kinesis-source-basic/readme.didact.md
@@ -46,7 +46,7 @@ You need the Apache Camel K CLI ("kamel") in order to access
all Camel K feature
**Knative installed on the cluster**
-The cluster also needs to have Knative installed and working. Refer to the
[official Knative documentation](https://knative.dev/docs/install/) for
information on how to install it in your cluster.
+The cluster also needs to have Knative installed and working. Refer to the
[official Knative documentation](https://knative.dev/v0.15-docs/install/) for
information on how to install it in your cluster.
[Check if the Knative Serving is
installed](didact://?commandId=vscode.didact.requirementCheck&text=kserving-project-check$$kubectl%20api-resources%20--api-group=serving.knative.dev$$kservice%2Cksvc&completion=Verified%20Knative%20services%20installation.
"Verifies if Knative Serving is installed"){.didact}
@@ -58,7 +58,7 @@ The cluster also needs to have Knative installed and working.
Refer to the [offi
**Knative Camel Source installed on the cluster**
-The cluster also needs to have installed the Knative Camel Source from the
camel.yaml in the [Eventing Sources release
page](https://github.com/knative/eventing-contrib/releases)
+The cluster also needs to have installed the Knative Camel Source from the
camel.yaml in the [Eventing Sources release
page](https://github.com/knative/eventing-contrib/releases/tag/v0.15.0)
[Check if the Knative Camel Source is
installed](didact://?commandId=vscode.didact.requirementCheck&text=kservice-project-check$$kubectl%20api-resources%20--api-group=sources.knative.dev$$camelsources&completion=Verified%20Knative%20Camel%20Source%20installation.
"Verifies if Knative Camel Source is installed"){.didact}
@@ -134,7 +134,7 @@ kubectl create secret generic aws-kinesis
--from-file=aws-kinesis.properties
```
([^
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20create%20secret%20generic%20aws-kinesis%20--from-file%3Daws-kinesis.properties&completion=secret%20%22aws-kinesis%22%20created.
"Create a secret with AWS Kinesis credentials"){.didact})
-As the example levareges [Knative Eventing
channels](https://knative.dev/docs/eventing/channels/), we need to create the
one that the example will use:
+As the example levareges [Knative Eventing
channels](https://knative.dev/v0.15-docs/eventing/channels/), we need to create
the one that the example will use:
```
kubectl apply -f aws-kinesis-channel.yaml
@@ -182,4 +182,4 @@ To cleanup everything, execute the following command:
```kubectl delete namespace aws-kinesis-source-basic```
-([^
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20delete%20namespace%20aws-kinesis-source-basic&completion=Removed%20the%20namespace%20from%20the%20cluster.
"Cleans up the cluster after running the example"){.didact})
\ No newline at end of file
+([^
execute](didact://?commandId=vscode.didact.sendNamedTerminalAString&text=camelTerm$$kubectl%20delete%20namespace%20aws-kinesis-source-basic&completion=Removed%20the%20namespace%20from%20the%20cluster.
"Cleans up the cluster after running the example"){.didact})
