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

Improve Starting Zilla with the CLI #1016

Closed
vordimous opened this issue May 9, 2024 · 1 comment · Fixed by #1042
Closed

Improve Starting Zilla with the CLI #1016

vordimous opened this issue May 9, 2024 · 1 comment · Fixed by #1042
Assignees
Labels
story Feature description from user's perspective

Comments

@vordimous
Copy link
Contributor

vordimous commented May 9, 2024

Describe the desired outcome from the user's perspective
As a developer, I want to run Zilla using the CLI tool and easily specify my zilla configuration.

Acceptance criteria

  • default start command should look in the current directory
  • zilla.yaml configs can be specified from a relative path
  • Help command reveals what my options are
  • unhide -e and add --exception-traces log name

Aditional Context

Current -c requires full path file://Users/username/path/to/zilla.yaml but doesn't support the java URI formate with ///, ex: file:///Users/username/path/to/zilla.yaml does not work.

@vordimous vordimous added the story Feature description from user's perspective label May 9, 2024
@vordimous
Copy link
Contributor Author

ex benthos cli:

% benthos help
NAME:
   benthos - A stream processor for mundane tasks - https://www.benthos.dev

USAGE:
   benthos [global options] command [command options] 

DESCRIPTION:
   Either run Benthos as a stream processor or choose a command:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Feature description from user's perspective
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants