You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The binary can take a lot of arguments/env variables, but currently, the following is the output of the call to parseable --help
Parseable v1.6.3
Cloud Native, log analytics platform for modern applications.
Join the community at https://logg.ing/community.
Commands:
local-store Start Parseable with a drive as storage
s3-store Start Parseable with S3 or compatible as storage
blob-store Start Parseable with Azure Blob storage
help Print this message or the help of the given subcommand(s)
Options:
-h, --help Print help
-V, --version Print version
No listing of possible commandline arguments is shown as would be expected from a commandline utility.
The text was updated successfully, but these errors were encountered:
@TwistingTwists the main idea behind this PR was to point out the available options at the global level, the idea is that we should print the common options for all subcommands, stuff like setting up kafka connector, hottier etc. But now that I think about it from a user perspective the following addition could be good enough to point the usage of each command:
The binary can take a lot of arguments/env variables, but currently, the following is the output of the call to
parseable --help
No listing of possible commandline arguments is shown as would be expected from a commandline utility.
The text was updated successfully, but these errors were encountered: