Closed cmhe closed 2 years ago
@clintoncwolfe any ideas?
/cc @dlouzan
I've reproduced the problem with Debian 11 virtualbox/vagrant, chef_solo with an empty runlist, kitchen_inspec 2.5.2, test-kitchen 3.2.2. Occurs with InSpec 4.24.32 (yours) and 4.56.20 (latest 4-series).
I'm looking into it.
Other than one docs commit to the README in February (https://github.com/inspec/kitchen-inspec/commit/c66a3955b3240a6e7cb71d19bf11df6ba1b157d3), I see no evidence that waivers functionality was ever implemented in kitchen-inspec.
Because This Has Never Worked, I'm going to take the liberty of renaming the config key to be "waiver_files" for consistency with the Chef Infra attribute and the InSpec CLI, and the other existing options.
Version:
Environment:
I am using kitchen-puppet and kitchen-vagrant to deploy to a virtual box debian image
Scenario:
Specify a waivers file to be used in the inspec execution, in order to skip some inspec controls.
Steps to Reproduce:
Used kitchen.yml:
Used inspec control (
test/integration/default/controls/test.rb
):Used waivers file (
test/integration/waivers.yml
):Expected Result:
A
kitchen test
run to finish successful.Actual Result:
kitchen test
run fails because the control was not skipped: