inspec/kitchen.vagrant.yml

---
driver:
  name: vagrant

provisioner:
  name: chef_solo

verifier:
  name: inspec
  sudo: true

lifecycle:
  pre_converge:
    - local: gem build inspec-core.gemspec --output test/kitchen/cookbooks/os_prepare/files/inspec-core-local.gem

platforms:
  - name: centos-6
  - name: centos-7
  - name: debian-8
  - name: debian-9
  - name: fedora-28
  - name: fedora-29
  - name: freebsd-11
  - name: opensuseleap-42
  - name: opensuseleap-15
  - name: ubuntu-16.04
  - name: ubuntu-18.04

suites:
  - name: default
    run_list:
      - recipe[os_prepare]
  - name: find_files
    run_list:
      - recipe[os_prepare::find_files]
    verifier:
      inspec_tests:
        - test/kitchen/policies/find_files
    excludes:
      - freebsd-11
run integration tests in docker 2016-05-10 17:23:11 +00:00			`---`
			`driver:`
			`name: vagrant`

			`provisioner:`
			`name: chef_solo`

			`verifier:`
			`name: inspec`
			`sudo: true`

Build the InSpec gem directly in Kitchen so we can run locally Before you had to kick off kitchen via Rake as the Rake task build the local gem we injected into the cookbook. Now we do it within Test Kitchen using a feature that didn't exist when this was all written. Also --output is your friend and greatly reduces the complexity of all this. Signed-off-by: Tim Smith <tsmith@chef.io> 2019-05-15 22:46:09 +00:00			`lifecycle:`
			`pre_converge:`
Update directory in kitchen configuration files Signed-off-by: Miah Johnson <miah@chia-pet.org> 2019-09-12 00:00:14 +00:00			`- local: gem build inspec-core.gemspec --output test/kitchen/cookbooks/os_prepare/files/inspec-core-local.gem`
Build the InSpec gem directly in Kitchen so we can run locally Before you had to kick off kitchen via Rake as the Rake task build the local gem we injected into the cookbook. Now we do it within Test Kitchen using a feature that didn't exist when this was all written. Also --output is your friend and greatly reduces the complexity of all this. Signed-off-by: Tim Smith <tsmith@chef.io> 2019-05-15 22:46:09 +00:00
run integration tests in docker 2016-05-10 17:23:11 +00:00			`platforms:`
Use the latest Bento boxes in the vagrant setup Use current Bento slugs and remove platforms we don't support as a company. Signed-off-by: Tim Smith <tsmith@chef.io> 2019-02-14 00:07:16 +00:00			`- name: centos-6`
			`- name: centos-7`
			`- name: debian-8`
			`- name: debian-9`
			`- name: fedora-28`
			`- name: fedora-29`
			`- name: freebsd-11`
			`- name: opensuseleap-42`
Add opensuseleap15 to the vagrant kitchen config Signed-off-by: Tim Smith <tsmith@chef.io> 2019-05-15 21:38:20 +00:00			`- name: opensuseleap-15`
Use the latest Bento boxes in the vagrant setup Use current Bento slugs and remove platforms we don't support as a company. Signed-off-by: Tim Smith <tsmith@chef.io> 2019-02-14 00:07:16 +00:00			`- name: ubuntu-16.04`
			`- name: ubuntu-18.04`
run integration tests in docker 2016-05-10 17:23:11 +00:00
			`suites:`
			`- name: default`
			`run_list:`
			`- recipe[os_prepare]`
Add wildcard support to `Utils::FindFiles` (#2159) Wildcards are evaluated prior to applying `sudo` permissions. This means that running `sudo find /some/path/.conf` will fail if the user does not have read permissions on `/some/path/` because the wildcard cannot expand before `sudo` is applied and `.conf` isn't a file. The solution for this is to run the command in a subshell that has the proper permissions (e.g. `sudo sh -c 'find /some/path/*.conf'`). This modifies `Utils::FindFiles` to use a subshell thus allowing wildcard support. This fixes #2157 Signed-off-by: Jerry Aldrich <jerryaldrichiii@gmail.com> 2017-09-23 07:17:34 +00:00			`- name: find_files`
			`run_list:`
			`- recipe[os_prepare::find_files]`
			`verifier:`
			`inspec_tests:`
Update directory in kitchen configuration files Signed-off-by: Miah Johnson <miah@chia-pet.org> 2019-09-12 00:00:14 +00:00			`- test/kitchen/policies/find_files`
Add wildcard support to `Utils::FindFiles` (#2159) Wildcards are evaluated prior to applying `sudo` permissions. This means that running `sudo find /some/path/.conf` will fail if the user does not have read permissions on `/some/path/` because the wildcard cannot expand before `sudo` is applied and `.conf` isn't a file. The solution for this is to run the command in a subshell that has the proper permissions (e.g. `sudo sh -c 'find /some/path/*.conf'`). This modifies `Utils::FindFiles` to use a subshell thus allowing wildcard support. This fixes #2157 Signed-off-by: Jerry Aldrich <jerryaldrichiii@gmail.com> 2017-09-23 07:17:34 +00:00			`excludes:`
Use the latest Bento boxes in the vagrant setup Use current Bento slugs and remove platforms we don't support as a company. Signed-off-by: Tim Smith <tsmith@chef.io> 2019-02-14 00:07:16 +00:00			`- freebsd-11`