use kafkacat name

Author: vordimous

README.md

@@ -75,7 +75,7 @@ Options:
 | [grpc.kafka.proxy](grpc.kafka.proxy)                         | Correlates gRPC requests and responses over separate Kafka topics                         |
 | [grpc.proxy](grpc.proxy)                                     | Proxies gRPC requests and responses sent to the gRPC server from a gRPC client            |
 | [http.filesystem](http.filesystem)                           | Serves files from a directory on the local filesystem                                     |
-| [http.json.validate](http.json.validate)                     | Proxy request sent to the HTTP server from an HTTP client with schema enforcement         |
+| [http.json.schema](http.json.schema)                     | Proxy request sent to the HTTP server from an HTTP client with schema enforcement         |
 | [http.jwt](http.jwt)                                         | Echoes request sent to the HTTP server from a JWT-authorized HTTP client                  |
 | [http.kafka.async](http.kafka.async)                         | Correlates HTTP requests and responses over separate Kafka topics, asynchronously         |
 | [http.kafka.avro.json](http.kafka.avro.json)                 | Validate messages while produce and fetch to a Kafka topic                                |

asyncapi.http.kafka.proxy/README.md

@@ -132,7 +132,7 @@ output:
 ```
 
 Copy the location, and create a `GET` async request using the location as the path.
-Note that the response will not return until you complete the following step to produce the response with `kcat`.
+Note that the response will not return until you complete the following step to produce the response with `kafkacat`.
 
 ```bash
 curl -v --location 'http://localhost:7114/customer;cid={correlationId}' \
@@ -158,15 +158,15 @@ output:
 {"id":200000,"username":"fehguy","status":"approved","address":[{"street":"437 Lytton","city":"Palo Alto","state":"CA","zip":"94301"}]}%
 ```
 
-Using `kcat` and the copied `correlation-id` produce the correlated message:
+Using `kafkacat` and the copied `correlation-id` produce the correlated message:
 
 ```sh
-echo '{"id":200000,"username":"fehguy","status":"approved","address":[{"street":"437 Lytton","city":"Palo Alto","state":"CA","zip":"94301"}]}' | docker compose -p zilla-asyncapi-http-kafka-proxy exec -T kcat \
-    kafkacat -P \
-         -b kafka:29092 \
-         -k "c234d09b-2fdf-4538-9d31-27c8e2912d4e" \
-         -t petstore-verified-customers \
-         -H "zilla:correlation-id={correlationId}"
+echo '{"id":200000,"username":"fehguy","status":"approved","address":[{"street":"437 Lytton","city":"Palo Alto","state":"CA","zip":"94301"}]}' | docker compose -p zilla-asyncapi-http-kafka-proxy exec -T kafkacat \
+  kafkacat -P \
+    -b kafka:29092 \
+    -k "c234d09b-2fdf-4538-9d31-27c8e2912d4e" \
+    -t petstore-verified-customers \
+    -H "zilla:correlation-id={correlationId}"
 ```
 
 ## Teardown

asyncapi.http.kafka.proxy/compose.yaml

@@ -78,7 +78,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

asyncapi.mqtt.kafka.proxy/compose.yaml

@@ -79,7 +79,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

asyncapi.sse.kafka.proxy/README.md

@@ -22,6 +22,7 @@ docker compose up -d
 ### Verify behaviour
 
 Using `curl` client connect to the SSE stream.
+
 ```bash
 curl -N --http2 -H "Accept:text/event-stream" -v "http://localhost:7114/events"
 ```
@@ -48,12 +49,13 @@ id:AQIAAg==
 data:{ "id": 1, "name": "Hello World!"}
 ```
 
-In another terminal window use `kcat` to publish to the `events` Kafka topic
+In another terminal window use `kafkacat` to publish to the `events` Kafka topic.
+
 ```bash
-echo '{ "id": 1, "name": "Hello World!"}' | docker compose -p zilla-asyncapi-sse-kafka-proxy exec -T kcat \
-    kafkacat -P \
-        -b kafka:29092 \
-        -k "1" -t events
+echo '{ "id": 1, "name": "Hello World!"}' | docker compose -p zilla-asyncapi-sse-kafka-proxy exec -T kafkacat \
+  kafkacat -P \
+    -b kafka:29092 \
+    -k "1" -t events
 ```
 
 On the `curl` client, the event should appear.

asyncapi.sse.kafka.proxy/compose.yaml

@@ -76,7 +76,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

grpc.kafka.echo/README.md

@@ -43,7 +43,7 @@ output:
 Verify the message payload, followed by a tombstone to mark the end of the request.
 
 ```bash
-docker compose -p zilla-grpc-kafka-echo exec kcat \
+docker compose -p zilla-grpc-kafka-echo exec kafkacat \
   kafkacat -C -b kafka:29092 -t echo-messages -J -u | jq .
 ```
 
@@ -112,7 +112,7 @@ Paste below message.
 Verify the message payloads, followed by a tombstone to mark the end of each request.
 
 ```bash
-docker compose -p zilla-grpc-kafka-echo exec kcat \
+docker compose -p zilla-grpc-kafka-echo exec kafkacat \
   kafkacat -C -b kafka:29092 -t echo-messages -J -u | jq .
 ```
 

grpc.kafka.echo/compose.yaml

@@ -76,7 +76,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

grpc.kafka.fanout/README.md

@@ -34,7 +34,7 @@ echo 'message: "test"' | protoc --encode=example.FanoutMessage proto/fanout.prot
 Produce protobuf message to Kafka topic, repeat to produce multiple messages.
 
 ```bash
-docker compose -p zilla-grpc-kafka-fanout exec kcat \
+docker compose -p zilla-grpc-kafka-fanout exec kafkacat \
   kafkacat -P -b kafka:29092 -t messages -k -e ./binary.data
 ```
 
@@ -93,7 +93,7 @@ docker compose -p zilla-grpc-kafka-fanout start zilla
 Then produce another protobuf message to Kafka, repeat to produce multiple messages.
 
 ```bash
-docker compose -p zilla-grpc-kafka-fanout exec kcat \
+docker compose -p zilla-grpc-kafka-fanout exec kafkacat \
   kafkacat -P -b kafka:29092 -t messages -k -e ./binary.data
 ```
 

grpc.kafka.fanout/compose.yaml

@@ -76,7 +76,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

grpc.kafka.proxy/README.md

@@ -42,7 +42,7 @@ output:
 Verify the message payload, followed by a tombstone to mark the end of the request.
 
 ```bash
-docker compose -p zilla-grpc-kafka-proxy exec kcat \
+docker compose -p zilla-grpc-kafka-proxy exec kafkacat \
   kafkacat -C -b kafka:29092 -t echo-requests -J -u | jq .
 ```
 
@@ -129,7 +129,7 @@ output:
 Verify the message payloads arrived in order, followed by a tombstone to mark the end of the response.
 
 ```bash
-docker compose -p zilla-grpc-kafka-proxy exec kcat \
+docker compose -p zilla-grpc-kafka-proxy exec kafkacat \
   kafkacat -C -b kafka:29092 -t echo-responses -J -u | jq .
 ```
 

grpc.kafka.proxy/compose.yaml

@@ -91,7 +91,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.json.validate/README.md renamed to http.json.schema/README.md

@@ -1,4 +1,4 @@
-# http.json.validate
+# http.json.schema
 
 Listens on https port `7114` and will response back whatever is hosted in `nginx` on that path after enforcing validation.
 

http.json.validate/compose.yaml renamed to http.json.schema/compose.yaml

@@ -1,4 +1,4 @@
-name: ${NAMESPACE:-zilla-http-schema-validate}
+name: ${NAMESPACE:-zilla-http-json-schema}
 services:
   zilla:
     image: ghcr.io/aklivity/zilla:${ZILLA_VERSION:-latest}

http.json.validate/nginx.conf renamed to http.json.schema/nginx.conf

@@ -0,0 +1,4 @@
+#!/bin/sh
+set -e
+
+docker compose -p "${NAMESPACE:-zilla-http-json-schema}" down --remove-orphans

http.json.validate/setup.sh renamed to http.json.schema/setup.sh

@@ -68,7 +68,7 @@ output:
 ```
 
 Use the returned location with correlation id specified by the `cid` param to attempt completion of the asynchronous request within `60 seconds`.
-Note that the response will not return until you complete the following step to produce the response with `kcat`.
+Note that the response will not return until you complete the following step to produce the response with `kafkacat`.
 
 ```bash
 curl -v \
@@ -90,7 +90,7 @@ output:
 Verify the request, then send the correlated response via the kafka `items-responses` topic.
 
 ```bash
-docker compose -p zilla-http-kafka-async exec kcat \
+docker compose -p zilla-http-kafka-async exec kafkacat \
   kafkacat -C -b kafka:29092 -t items-requests -J -u | jq .
 ```
 
@@ -135,7 +135,7 @@ output:
 Make sure to propagate the request message `zilla:correlation-id` header verbatim as a response message `zilla:correlation-id` header.
 
 ```bash
-echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-async exec -T kcat \
+echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-async exec -T kafkacat \
   kafkacat -P \
     -b kafka:29092 \
     -t items-responses \
@@ -157,7 +157,7 @@ The previous asynchronous request will complete with `200 OK` if done within `60
 Verify the response via the kafka `items-responses` topic.
 
 ```bash
-docker compose -p zilla-http-kafka-async exec kcat \
+docker compose -p zilla-http-kafka-async exec kafkacat \
   kafkacat -C -b kafka:29092 -t items-responses -J -u | jq .
 ```
 

http.json.schema/teardown.sh

@@ -75,7 +75,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.json.validate/www/demo.html renamed to http.json.schema/www/demo.html

@@ -105,7 +105,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.json.validate/www/invalid.json renamed to http.json.schema/www/invalid.json

@@ -83,7 +83,7 @@ output:
 Produce an item snapshot to the kafka topic.
 
 ```bash
-echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-cache exec -T kcat \
+echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-cache exec -T kafkacat \
   kafkacat -P \
     -b kafka:29092 \
     -t items-snapshots \
@@ -181,7 +181,7 @@ Before the 60 seconds elapses, produce an updated item snapshot to the kafka top
 The prefer wait http request returns the new item snapshot with updated `etag` as shown above.
 
 ```bash
-echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-cache exec -T kcat \
+echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-cache exec -T kafkacat \
   kafkacat -P \
     -b kafka:29092 \
     -t items-snapshots \

http.json.validate/www/style.css renamed to http.json.schema/www/style.css

@@ -74,7 +74,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.json.validate/www/valid.json renamed to http.json.schema/www/valid.json

@@ -74,7 +74,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.json.validate/zilla.yaml renamed to http.json.schema/zilla.yaml

@@ -45,7 +45,7 @@ output:
 Verify that the event has been produced to the `events` Kafka topic.
 
 ```bash
-docker compose -p zilla-http-kafka-oneway exec kcat \
+docker compose -p zilla-http-kafka-oneway exec kafkacat \
   kafkacat -C -b kafka:29092 -t events -J -u | jq .
 ```
 

http.json.validate/teardown.sh

@@ -75,7 +75,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.kafka.async/README.md

@@ -75,7 +75,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.kafka.async/compose.yaml

@@ -18,10 +18,10 @@ docker compose up -d
 
 ## Watch kafka
 
-Open the [Kafka UI](http://localhost:8080/ui/clusters/local/all-topics/my-requests/messages?limit=100&mode=TAILING) or run the kcat command:
+Open the [Kafka UI](http://localhost:8080/ui/clusters/local/all-topics/my-requests/messages?limit=100&mode=TAILING) or run the kafkacat command:
 
 ```bash
-docker compose -p zilla-http-kafka-proto-oneway exec kcat \
+docker compose -p zilla-http-kafka-proto-oneway exec kafkacat \
   kafkacat -b kafka:29092 -C -f 'Key:Message | %k:%s\n Headers | %h \n\n' -t my-requests
 ```
 

http.kafka.avro.json/compose.yaml

@@ -75,7 +75,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true

http.kafka.cache/README.md

@@ -24,7 +24,7 @@ This will:
 ## Verify behavior
 
 Send a `PUT` request for a specific item.
-Note that the response will not return until you complete the following step to produce the response with `kcat`.
+Note that the response will not return until you complete the following step to produce the response with `kafkacat`.
 
 ```bash
 curl -v \
@@ -53,7 +53,7 @@ Fetch the request message, then send the correlated response via the Kafka UI [i
 - or from the command line
 
   ```bash
-  docker compose -p zilla-http-kafka-sync exec kcat \
+  docker compose -p zilla-http-kafka-sync exec kafkacat \
     kafkacat -b kafka:29092 -C -f 'Key:Message | %k:%s\n Headers | %h \n\n' -t items-requests
   ```
 
@@ -67,7 +67,7 @@ Produce the the correlated response message via the Kafka UI [items-responses](h
 Make sure to propagate the request message `zilla:correlation-id` header, found in the request message, verbatim as a response message `zilla:correlation-id` header.
 
 ```bash
-echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-sync exec -T kcat \
+echo "{\"greeting\":\"Hello, world `date`\"}" | docker compose -p zilla-http-kafka-sync exec -T kafkacat \
   kafkacat -P \
   -b kafka:29092 \
   -t items-responses \
@@ -92,7 +92,7 @@ Verify the response response via the Kafka UI [items-responses](http://localhost
 - or from the command line
 
   ```bash
-  docker compose -p zilla-http-kafka-sync exec kcat \
+  docker compose -p zilla-http-kafka-sync exec kafkacat \
   kafkacat -b kafka:29092 -C -f 'Key:Message | %k:%s\n Headers | %h \n\n' -t items-responses
   ```
 

http.kafka.cache/compose.yaml

@@ -75,7 +75,7 @@ services:
       KAFKA_CLUSTERS_0_NAME: local
       KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
 
-  kcat:
+  kafkacat:
     image: confluentinc/cp-kafkacat:7.1.9
     command: "bash"
     stdin_open: true