-
Notifications
You must be signed in to change notification settings - Fork 50
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
Use positionnal argument for directory/file input/output path #232
Conversation
Co-authored-by: Edouard Schweisguth <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a little nit on wording
pkg/cmd/dump.go
Outdated
cmd.Flags().String("output-dir", "", "Directory to dump the data") | ||
viper.BindPFlag(config.CollectorFileDirectory, cmd.Flags().Lookup("output-dir")) //nolint: errcheck | ||
cmd.MarkFlagRequired("output-dir") //nolint: errcheck | ||
cmd.Flags().Bool("no-compress", false, "Enable compression for the dumped data (generates a tar.gz file)") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel the name no-compress
tells the opposite of Enable compression
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it is fixed
…DataDog/kubehound into jt-dd/modifying-inputs-args-flags
Removing the flags for the input/output for
ingest local
anddump local
. Now it will get passed through the first argument:kubehound dump local [directory to dump the data]
kubehound ingest local [directory or tar.gz path] --cluster <cluster_name>
Also now the default behavior is to create a compressed file. So the
--compress
has been changed to--no-compress
.Note: another PR will be made for the docs