-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
✨ Implement Chef InSpec Parser #9329
Conversation
Contextual Security AnalysisAs DryRun Security performs checks, we’ll summarize them here. You can always dive into the detailed results in the section below for checks.
Chat with your AI-powered Security Buddy by typing Install and configure more repositories at DryRun Security |
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.
Approved
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.
A couple notes on this one...
Thank you for the review @cneill. I fixed your issues. |
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.
Thanks! Approved
I can't see your comment @Maffooch that you approve this. |
Done |
The outputs of Chef Inspec are called "reporters". These include json format but no "logs". |
I never used Chef Ispec Parser, just fulfilled the PR according to the linked issue description. |
@MirceaLutic I've never used Chef Inspect either but looking at the unit test files: I'd suggest you compare the structure of what you're seeing to those unit test file. I may be as simple as changing the file extension 🤷 |
see issue #6990