rpk connect test

Run unit tests defined in Redpanda Connect configuration files to verify pipeline behavior.

If one or more tests fail, the command reports the errors and exits with status code 1.

Usage

rpk connect test [flags]

Examples

This section provides examples of how to use rpk connect test.

Example.

rpk connect test ./path/to/configs/...

Example.

rpk connect test ./foo_configs/*.yaml ./bar_configs/*.yaml

Example.

rpk connect test ./foo.yaml

Flags

Value Type Description

--log

string

allow components to write logs at a provided level to stdout.

-v, --verbose

bool

print all test case names before they are executed.

-r, --resources

strings

pull in extra resources from a file, which can be referenced the same as resources defined in the main config, supports glob patterns (requires quotes).

-e, --env-file

strings

import environment variables from a dotenv file.

-t, --templates

strings

EXPERIMENTAL: import Redpanda Connect templates, supports glob patterns (requires quotes).

Global flags

Value Type Description

--config

string

Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml.

-X, --config-opt

stringArray

Override rpk configuration settings; -X help for detail or -X list for terser detail.

--ignore-profile

bool

Ignore rpk.yaml and redpanda.yaml; use default settings.

--profile

string

rpk profile to use.

-v, --verbose

bool

Enable verbose logging.

Suggested reading