Sha256: e6b2ff907049edaae765ae2ce5eb18bcba9191f2a5060e4c04f2d25b6ca8212c
Contents?: true
Size: 1.26 KB
Versions: 32
Compression:
Stored size: 1.26 KB
Contents
---
title: About kitchen-inspec
---
# kitchen-inspec
Use InSpec as a Kitchen verifier with `kitchen-inspec`.
Add the InSpec verifier to the `.kitchen.yml` file:
verifier:
name: inspec
Use a compliance profile from the Chef Compliance server:
suites:
- name: compliance
run_list:
- recipe[ssh-hardening::default]
verifier:
inspec_tests:
- compliance://base/ssh
and then run the following command:
$ inspec compliance login https://compliance.test --user admin --insecure --token ''
where `--insecure` is required when using self-signed certificates.
Use a compliance profile from the Chef Supermarket:
suites:
- name: supermarket
run_list:
- recipe[ssh-hardening::default]
verifier:
inspec_tests:
- supermarket://dev-sec/ssh-baseline
Use InSpec tests from the local file system:
suites:
- name: local
run_list:
- recipe[my_cookbook::default]
verifier:
inspec_tests:
- test/integration/default
Check out [Detect and correct with Test Kitchen](https://learn.chef.io/modules/detect-correct-kitchen#/) on Learn Chef Rally for a hands-on look at how to use Test Kitchen to run InSpec profiles.
Version data entries
32 entries across 32 versions & 2 rubygems