Skip to content
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

Closed
aaronlippold opened this issue Mar 22, 2016 · 5 comments
Closed

--controls flag should be supported in all inspec commands #568

aaronlippold opened this issue Mar 22, 2016 · 5 comments

Comments

@aaronlippold
Copy link
Collaborator

@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=...
...

@arlimus
Copy link
Contributor

arlimus commented Mar 22, 2016

👍 , we can tackle it for json fairly quickly ;)
We'll need to collect a list of all the places where this is relevant, but can get started with something as specific as json right away.

@aaronlippold
Copy link
Collaborator Author

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.

@arlimus
Copy link
Contributor

arlimus commented Mar 25, 2016

let's use your list:

@arlimus
Copy link
Contributor

arlimus commented Mar 25, 2016

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

@arlimus
Copy link
Contributor

arlimus commented Mar 25, 2016

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 arlimus closed this as completed Mar 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants