Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI references the wrong binary name #2639

Open
KasonBraley opened this issue Jun 6, 2024 · 0 comments · May be fixed by #2640
Open

CLI references the wrong binary name #2639

KasonBraley opened this issue Jun 6, 2024 · 0 comments · May be fixed by #2640
Labels

Comments

@KasonBraley
Copy link

The output from rpk connect --help references redpanda-connect as the command to run, I think it's supposed to be rpk connect.

~/n/benthos> rpk connect --help
NAME:
   redpanda-connect - A stream processor for mundane tasks - https://docs.redpanda.com/redpanda-connect

USAGE:
   redpanda-connect [global options] command [command options] 

DESCRIPTION:
   Either run Redpanda Connect as a stream processor or choose a command:

     redpanda-connect list inputs
     redpanda-connect create kafka//file > ./config.yaml
     redpanda-connect -c ./config.yaml
     redpanda-connect -r "./production/*.yaml" -c ./config.yaml

COMMANDS:
   echo      Parse a config file and echo back a normalised version
   lint      Parse Redpanda Connect configs and report any linting errors
   run       Run Redpanda Connect in normal mode against a specified config file
   streams   Run Redpanda Connect in streams mode
   list      List all Redpanda Connect component types
   create    Create a new Redpanda Connect config
   test      Execute Redpanda Connect unit tests
   template  Interact and generate Redpanda Connect templates
   blobl     Execute a Redpanda Connect mapping on documents consumed via stdin
   studio    Interact with Benthos studio (https://studio.benthos.dev)
   help, h   Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --version, -v                                                                                                                    display version info, then exit (default: false)
   --config value, -c value                                                                                                         a path to a configuration file
   --log.level value                                                                                                                override the configured log level, options are: off, error, warn, info, debug, trace
   --set "metrics.type=prometheus", -s "metrics.type=prometheus" [ --set "metrics.type=prometheus", -s "metrics.type=prometheus" ]  set a field (identified by a dot path) in the main configuration file, e.g. "metrics.type=promethe
us"
   --resources value, -r value [ --resources value, -r value ]                                                                      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)
   --chilled                                                                                                                        continue to execute a config containing linter errors (default: false)
   --watcher, -w                                                                                                                    EXPERIMENTAL: watch config files for changes and automatically apply them (default: false)
   --env-file value, -e value [ --env-file value, -e value ]                                                                        import environment variables from a dotenv file
   --templates value, -t value [ --templates value, -t value ]                                                                      EXPERIMENTAL: import Redpanda Connect templates, supports glob patterns (requires quotes)
   --help, -h               
@KasonBraley KasonBraley linked a pull request Jun 6, 2024 that will close this issue
@mihaitodor mihaitodor added the bug label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants