Closed DeLaBatth closed 9 months ago
Hello @DeLaBatth -- Yes, we should continue to provide the option to write the json to a file. We welcome contributions.
In the docker run command we were using -it
which was messing up stdout and stderr, using -i
instead of -it
fixed the issue also we were printing summary in case of json output in wrong place
both issues are fixed and docs are update in PR https://github.com/deepfence/YaraHunter/pull/73
PR works great, thanks a lot @gnmahanth, but we need to update following doc files also:
docs/docs/yarahunter/configure/cli.md
docs/docs/yarahunter/configure/output.md
docs/docs/yarahunter/index.md
docs/docs/yarahunter/quickstart.md
I have added a comment.
Thanks @shyam-dev for your answer.
Hi!
Since release v2.0.0 (see commit) Json output can no longer be stored in output file. However, the opposite is specified in the documentation:
Readme.md
anddocs/docs/yarahunter/configure/output.md
:With yara-hunter v2.0.0: I have this error when I specified flag
--json-filename
:Message
flag provided but not defined: -json-filename
is caused by removing of flag--json-filename
in this commit: https://github.com/deepfence/YaraHunter/commit/48571c79c26c44c96ffd20e45d11bf8e739c6096.Question is:
--json-filename
andoutput-path
?If "Yes", I can do MR to update the documentation. If not, I can also do MR to fix this behavior and generate a json output file thanks to flag
--output=json
I will be happy to contribute, and I just want to be sure to respect the vision of previous contributors, about this topic.
The current flag
--output=json
can be used to generate json output file, like this:But the problem is that there are also logs info in this file: