-
Notifications
You must be signed in to change notification settings - Fork 26
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
Any tool to read the output JSON file? #70
Comments
hi @strus38 Thank you for raising the question. If you are using it via the playbook to can set the variable This will produce a much more human readable output with all failures in a section of the file. There is currently in works a method to present/sort/report on this which we hope we are able to show soon. I hope that helps. Many thanks uk-bolly |
Thanks!!
|
hi @strus38 Im not using the json file as mentioned i changed the format to documentation for an easier reading file. The PR should be moved to the correct branch in the next day or so. Let me know if this is still not working. many thanks uk-bolly |
Hi @strus38 The PR was merged last week so i am hoping with the details above this has helped with this issue? Please let us know if this resolves your issue? thanks uk-bolly |
Question
Very new to this project, I executed the CIS-RHEL8 audit, and the result is a JSON file, is there a tool to view it in another format (easier to see SUCCESS/FAILURE)?
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: