You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/09/16 16:27:14 UTC

[camel-kafka-connector-examples] branch fix-aws2-sqs-sink created (now 6b97ebc)

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a change to branch fix-aws2-sqs-sink
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector-examples.git.


      at 6b97ebc  AWS2-SQS Sink example: It must be oc and not kubectl

This branch includes the following new commits:

     new 6b97ebc  AWS2-SQS Sink example: It must be oc and not kubectl

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[camel-kafka-connector-examples] 01/01: AWS2-SQS Sink example: It must be oc and not kubectl

Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch fix-aws2-sqs-sink
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector-examples.git

commit 6b97ebc65a66583274d9e80ef396cc88072434d1
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed Sep 16 18:26:50 2020 +0200

    AWS2-SQS Sink example: It must be oc and not kubectl
---
 aws2-sqs/aws2-sqs-sink/README.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/aws2-sqs/aws2-sqs-sink/README.adoc b/aws2-sqs/aws2-sqs-sink/README.adoc
index 7b80b14..65b1305 100644
--- a/aws2-sqs/aws2-sqs-sink/README.adoc
+++ b/aws2-sqs/aws2-sqs-sink/README.adoc
@@ -159,7 +159,7 @@ To check the available connector plugins, you can run the following command:
 
 [source,bash,options="nowrap"]
 ----
-oc exec -i -c kafka my-cluster-kafka-0 -- curl -s http://my-connect-cluster-connect-api:8083/connector-plugins
+oc exec -i `oc get pods --field-selector status.phase=Running -l strimzi.io/name=my-connect-cluster-connect -o=jsonpath='{.items[0].metadata.name}'` -- curl -s http://my-connect-cluster-connect-api:8083/connector-plugins
 ----
 
 You should see something like this:
@@ -203,7 +203,7 @@ You can check the status of the connector using
 
 [source,bash,options="nowrap"]
 ----
-oc exec -i -c kafka my-cluster-kafka-0 -- curl -s http://my-connect-cluster-connect-api:8083/connectors/sqs-sink-connector/status
+oc exec -i `oc get pods --field-selector status.phase=Running -l strimzi.io/name=my-connect-cluster-connect -o=jsonpath='{.items[0].metadata.name}'` -- curl -s http://my-connect-cluster-connect-api:8083/connectors/sqs-sink-connector/status
 ----
 
 ### Check enqueued messages