Use the _kafka_supporting
user! in my case lmolteni_kafka_supporting
on console.redhat.com
rhoas login
rhoas kafka list
rhoas kafka create --name=lucamolteni-managedconnector
rhoas kafka describe
wait for the kafka instance to be ready
rhoas service-account list
rhoas service-account create --output-file=./service-acct-credentials.json --file-format=json --overwrite --short-description= lucamolteni-managedconnector-serviceaccount
rhoas service-account list | grep lucamolteni-managedconnector-serviceaccount
export SERVICEACCOUNT=$(cat ./service-acct-credentials.json | jq -r '.clientID')
rhoas kafka acl grant-access --consumer --producer \
--service-account $SERVICEACCOUNT --topic-prefix slacktopic --group all
export BOOTSTRAPSERVER=$(rhoas kafka describe --name=lucamolteni-managedconnector | jq -r '.bootstrap_server_host')
export PASSWORD=$(cat ./service-acct-credentials.json | jq -r '.clientSecret')
rhoas kafka topic create --name=slacktopic
Now go on the managed connector staging area (VPN) and create a sink connector using the same service account created before due to MGDSTRM-6181
kcat -t slacktopic -b "$BOOTSTRAPSERVER" \
-X security.protocol=SASL_SSL -X sasl.mechanisms=PLAIN \
-X sasl.username="$SERVICEACCOUNT" \
-X sasl.password="$PASSWORD" -C
kcat -t slacktopic -b "$BOOTSTRAPSERVER" \
-X security.protocol=SASL_SSL -X sasl.mechanisms=PLAIN \
-X sasl.username="$SERVICEACCOUNT" \
-X sasl.password="$PASSWORD" -P