confluent local services connect connector config¶

Important

The confluent local commands are intended for a single-node development environment and are not suitable for a production environment. The data that are produced are transient and are intended to be temporary. For production-ready workflows, see Confluent Platform.

Description¶

View or set connector configurations.

confluent local services connect connector config <connector-name> [flags]

Tip

You must export the path as an environment variable for each terminal session, or set the path to your Confluent Platform installation in your shell profile. For example:

cat ~/.bash_profile
export CONFLUENT_HOME=<path-to-confluent>
export PATH="${CONFLUENT_HOME}/bin:$PATH"

Flags¶

-c, --config string   Configuration file for a connector.

Global Flags¶

-h, --help            Show help for this command.
    --unsafe-trace    Equivalent to -vvvv, but also log HTTP requests and responses which might contain plaintext secrets.
-v, --verbose count   Increase verbosity (-v for warn, -vv for info, -vvv for debug, -vvvv for trace).

Examples¶

Print the current configuration of a connector named s3-sink:

confluent local services connect connector config s3-sink

Configure a connector named wikipedia-file-source by passing its configuration properties in JSON format.

confluent local services connect connector config wikipedia-file-source --config <path-to-connector>/wikipedia-file-source.json

Configure a connector named wikipedia-file-source by passing its configuration properties as Java properties.

confluent local services connect connector config wikipedia-file-source --config <path-to-connector>/wikipedia-file-source.properties