-
Notifications
You must be signed in to change notification settings - Fork 682
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
--controls flag should be supported in all inspec commands #568
Comments
👍 , we can tackle it for json fairly quickly ;) |
I would say that json, then compliance then supermarket would be the right order. Given that would be the way the product line would want to grow the support. |
let's use your list:
|
from cursory checking (@chris-rock is off right now) I can see controls support in both compliance and supermarket: > inspec compliance help exec
Usage:
inspec exec PROFILE
...
[--controls=one two three] # A list of controls to run. Ignore all other tests. @aaronlippold please let me know if this isn't working, we should track it in a separate issue |
Covered all items. Please let us know if there is more to cover. If any of the existing methods have bugs, let's create new issues. Thank you @aaronlippold ! 👍 |
@arlimus / @chris-rock : Support for the new --controls flag seems to have been left out for the other inspec subcommands.
My team is using the inspec json subcommand to parse out the elements of a profile for application integration and the ability to slice out specific controls would be very useful.
inspec json --controls="a b c"
inspec supermarket --controls=...
inspec compliance --controls=...
...
The text was updated successfully, but these errors were encountered: