Confluent kafka client-config not found

Clients Java Clients
1

I’m following the Kafka-Connect-101 (Create Confluent Managed Kafka Connectors with the Connect API) and I can’t figure out what’s wrong with the following:
Command 14 at tutorial:
confluent kafka client-config create java --sr-apikey <sr API key> --sr-apisecret <sr API secret> | tee $HOME/.confluent/java.config

The script is outdated since the documentation here has changed --sr-apikey to full form (confluent kafka client-config create java | Confluent Documentation)

I’m basically getting command not found for client-config have I missed a step or is there other issue:

# confluent kafka client-config
Manage Apache Kafka.

Usage:
  confluent kafka [command]

Available Commands:
  acl            Manage Kafka ACLs.
  cluster        Manage Kafka clusters.
  link           Manages inter-cluster links.
  mirror         Manages cluster linking mirror topics.
  region         Manage Confluent Cloud regions.
  topic          Manage Kafka topics.

Global Flags:
  -h, --help            Show help for this command.
  -v, --verbose count   Increase verbosity (-v for warn, -vv for info, -vvv for debug, -vvvv for trace).

Use "confluent kafka [command] --help" for more information about a command.
2

I am having the same issue, were you able to resolve this by any chance? Thank you!

3

What version of the CLI are you using (confluent version)? On the latest 3.40.0 you should see the client-config option if you’re logged into Confluent Cloud and run confluent kafka --help.

The script is outdated since the documentation here has changed --sr-apikey to full form

Yes, we will fix this in the module. The syntax with the latest CLI is:

confluent kafka client-config create java  \
    --api-key <API KEY> \
    --api-secret <SECRET> \
    --schema-registry-api-key <SR API KEY> \
    --schema-registry-api-secret <SR SECRET>
4

I’ve tried to do this using confluence kafka version 7.1.1 and still happening, Anyone have any way to fix this problem?

5

@djimenezt the steps below (note: API key creation left out) are working for me. How do they differ from yours? You are doing this with the CLI packaged in Confluent Platform 7.1.1 but logged into Confluent Cloud, right?

 curl -O https://packages.confluent.io/archive/7.1/confluent-7.1.1.zip\n
 unzip confluent-7.1.1.zip
 cd confluent-7.1.1/bin
 ./confluent login --prompt

 <enter credentials>

 confluent environment list
 confluent environment use env-******
 confluent kafka cluster list
 confluent kafka cluster use lkc-******
 confluent kafka client-config create java \
    --api-key <API_KEY> --api-secret <API_SECRET> \
    --schema-registry-api-key <SR_API_KEY> \
    --schema-registry-api-secret <SR_API_SECRET>
6

Thank you for your answer @dtroiano , I’ve logged into Clonfluent Cloud and I’ve followed your steps and I’ve got the follow error

confluent kafka client-config create java
–api-key AU********* --api-secret y2lrC*****
–schema-registry-api-key T6******
–schema-registry-api-secret Jp/N******

Error: unknown flag: --api-key
Usage:
confluent kafka [command]

Available Commands:
acl Manage Kafka ACLs.
cluster Manage Kafka clusters.
link Manages inter-cluster links.
mirror Manages cluster linking mirror topics.
region Manage Confluent Cloud regions.
topic Manage Kafka topics.

Global Flags:
-h, --help Show help for this command.
-v, --verbose count Increase verbosity (-v for warn, -vv for info, -vvv for debug, -vvvv for trace).

Use “confluent kafka [command] --help” for more information about a command.

7

@djimenezt could you please share the output of confluent version?

8

Same error. My output is:

$ confluent version
confluent - Confluent CLI

Version:     v2.6.1
Git Ref:     6d920590
Build Date:  2022-02-18T06:14:21Z
Go Version:  go1.17.6 (linux/amd64)
Development: false
9

@BanksAT_SD It doesn’t look like confluent kafka client-config... is supported in 2.6.1 (command reference). I would definitely recommend a CLI upgrade since 2.6.1 two major versions behind (the current latest is 4.26.1). There have been a lot of breaking changes, and IIRC some commands that won’t even work anymore due to backend APIs getting sunset.