Sha256: cc8abe88f4f3e1e6e1e296c84567a0e891a31f6da642384ccc6bd5f6d4b8626a

Contents?: true

Size: 1.31 KB

Versions: 3

Compression:

Stored size: 1.31 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

3 entries across 3 versions & 1 rubygems

Version Path
inspec-2.1.81 docs/plugin_kitchen_inspec.md
inspec-2.1.21 docs/plugin_kitchen_inspec.md
inspec-2.1.10 docs/plugin_kitchen_inspec.md