-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add the 'reporter' configuration option to kitchen-inspec #183
Conversation
Signed-off-by: Tim Pringle <tim.pringle@poweshell.amsterdam>
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 for this @tim-pringle !
Hi @jquick, I'm curious what else is needed to get this PR approved/merged? I've tested this branch locally with good results. Thanks! |
@danielcbright - Hey, ill see if I can get another approval and get some of these pushed out and released this week. Thanks for the push. |
Thanks for creating this PR! Looks like it addresses #177 and is ready to go. Is there anything further needed to get the additional approval? |
Thanks guys, merging now but we wont be able to have a new version pushed out till next week after ChefConf. |
Is there some way to make the reporter filename based on platform and suite names? Also, this might make #137 obsolete |
Since #183 the reporter feature can and should be used to define the InSpec output. Signed-off-by: Lukas Schmidt <Lukas.Schmidt@kisters.de>
Here is an example how you can generate names more flexible:
|
Signed-off-by: Tim Pringle tim.pringle@poweshell.amsterdam
The --format option is being being deprecated and will be removed in inspec 3.0.
This change allows the use of the --reporter parameter in a Kitchen config file.
Usage example:
NB: Unlike 'format', 'reporter' is always parsed as a collection. As such it must be written appropriately in your .yml file when there is only one parameter as well.