inspec 1.51.18 → 1.51.21

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d296647cc15aa87bd0a740bf0681f5baafa00838
-  data.tar.gz: 7ed7686d7383fef72a2b2fe176f5b6e220b515f5
+  metadata.gz: 3379b4b69a099b07df2099525af24ea73e167141
+  data.tar.gz: f22f228ca686117c6737040d292c6311b09bc12f
 SHA512:
-  metadata.gz: b73ccef73c2b6cc8b472092c15d3176671868d48b6975fc0e754f8191c82a2c3f96690723fbfdddcb4ecfaef61deb234cc306e04260586780d9328817bd1b4c4
-  data.tar.gz: a4d6825cc146416ea6ed1f98f919f03233850f4c7f1b4c9fa67f20d829a236fe2f74ff3cfa75b88555058528f11557ccc802627dd6bc2459e0c873d83eb107c1
+  metadata.gz: 04cf3f6b6265c41df661c540bdc3c35553c6cd425a7620c27dfa4aa18cc8bf87a9be7f64619c4767b53ad9f604d3722211839161d973f128b4325ca9867a0f91
+  data.tar.gz: efa9fd7444b45de81d1f525829cfa8c48e7c8a2fc09038ed48990acf92746405d8ef1dc6622377fa8c885dc2842540e32dbb27a67394ce4768384484f63af50a

data/CHANGELOG.md

@@ -1,22 +1,30 @@
 # Change Log
 <!-- usage documentation: http://expeditor-docs.es.chef.io/configuration/changelog/ -->
-<!-- latest_release 1.51.18 -->
-## [v1.51.18](https://github.com/chef/inspec/tree/v1.51.18) (2018-02-12)
+<!-- latest_release 1.51.21 -->
+## [v1.51.21](https://github.com/chef/inspec/tree/v1.51.21) (2018-02-18)
 
 #### Merged Pull Requests
-- Add json fields to schema and add tests. [#2618](https://github.com/chef/inspec/pull/2618) ([jquick](https://github.com/jquick))
+- Fix legacy reporter output to file (inspec-v1.x) [#2689](https://github.com/chef/inspec/pull/2689) ([jquick](https://github.com/jquick))
 <!-- latest_release -->
 
-<!-- release_rollup since=1.51.15 -->
-### Changes since 1.51.15 release
+<!-- release_rollup since=1.51.18 -->
+### Changes since 1.51.18 release
 
 #### Merged Pull Requests
-- Add json fields to schema and add tests. [#2618](https://github.com/chef/inspec/pull/2618) ([jquick](https://github.com/jquick)) <!-- 1.51.18 -->
-- Allow ad-hoc runners to use rspec formats. [#2621](https://github.com/chef/inspec/pull/2621) ([jquick](https://github.com/jquick)) <!-- 1.51.17 -->
-- Force a default reporter for ad-hoc runners [#2610](https://github.com/chef/inspec/pull/2610) ([jquick](https://github.com/jquick)) <!-- 1.51.16 -->
+- Fix legacy reporter output to file (inspec-v1.x) [#2689](https://github.com/chef/inspec/pull/2689) ([jquick](https://github.com/jquick)) <!-- 1.51.21 -->
+- package resource: Fix Windows package detection [#2624](https://github.com/chef/inspec/pull/2624) ([jerryaldrichiii](https://github.com/jerryaldrichiii)) <!-- 1.51.20 -->
+- Fix the /private/var osx issue causing functional tests to fail [#2616](https://github.com/chef/inspec/pull/2616) ([jquick](https://github.com/jquick)) <!-- 1.51.19 -->
 <!-- release_rollup -->
 
 <!-- latest_stable_release -->
+## [v1.51.18](https://github.com/chef/inspec/tree/v1.51.18) (2018-02-12)
+
+#### Merged Pull Requests
+- Force a default reporter for ad-hoc runners [#2610](https://github.com/chef/inspec/pull/2610) ([jquick](https://github.com/jquick))
+- Allow ad-hoc runners to use rspec formats. [#2621](https://github.com/chef/inspec/pull/2621) ([jquick](https://github.com/jquick))
+- Add json fields to schema and add tests. [#2618](https://github.com/chef/inspec/pull/2618) ([jquick](https://github.com/jquick))
+<!-- latest_stable_release -->
+
 ## [v1.51.15](https://github.com/chef/inspec/tree/v1.51.15) (2018-02-09)
 
 #### Merged Pull Requests
@@ -29,7 +37,6 @@
 - Refactors grub_conf doc sligtly; adds os metadata [#2537](https://github.com/chef/inspec/pull/2537) ([kagarmoe](https://github.com/kagarmoe))
 - Use the version of LicenseScout that comes with the Omnibus gem. [#2554](https://github.com/chef/inspec/pull/2554) ([tduffield](https://github.com/tduffield))
 - Fix runner report and json newline [#2601](https://github.com/chef/inspec/pull/2601) ([jquick](https://github.com/jquick))
-<!-- latest_stable_release -->
 
 ## [v1.51.6](https://github.com/chef/inspec/tree/v1.51.6) (2018-02-08)
 

data/docs/reporters.md

@@ -0,0 +1,105 @@
+---
+title: InSpec Reporters
+---
+
+# InSpec Reporters
+
+Introduced in InSpec 1.51.6
+
+InSpec allows you to output your test results to one or more reporters. You can configure the reporter(s) using either the `--json-config` option or the `--reporter` option. While you can configure multiple reporters to write to different files, only one reporter can output to the screen(stdout).
+
+## Syntax
+
+You can specify one or more reporters using the `--reporter` cli flag. You can also specify a output by appending a path seperated by a colon.
+
+Output json to screen.
+
+```bash
+inspec exec --reporter json
+or
+inspec exec --reporter json:-
+```
+
+Output cli to screen and write json to a file.
+
+```bash
+inspec exec --reporter cli json:/tmp/output.json
+```
+
+Output nothing to screen and write junit and html to a file.
+
+```bash
+inspec exec --reporter junit:/tmp/junit.xml html:www/index.html
+```
+
+Output json to screen and write to a file. Write junit to a file.
+
+```bash
+inspec exec --reporter json junit:/tmp/junit.xml | tee out.json
+```
+
+If you are using the cli option `--json-config` you can also set reporters.
+
+Output cli to screen.
+
+```json
+{
+    "reporter": {
+        "cli" : {
+            "stdout" : true
+        }
+    }
+}
+```
+
+Output cli to screen and write json to a file.
+
+```json
+{
+    "reporter": {
+        "cli" : {
+            "stdout" : true
+        },
+        "json" : {
+            "file" : "/tmp/output.json",
+            "stdout" : false
+        }
+    }
+}
+```
+
+## Supported Reporters
+
+The following are the current supported reporters:
+
+### cli
+
+This is the basic text base report. It includes details about which tests passed and failed and includes an overall summary at the end.
+
+### json
+
+This reporter includes all information about the profiles and test results in standard json format.
+
+### json-min
+
+This reporter is a redacted version of the json and only includes test results.
+
+### documentation
+
+This reporter is a very minimal text base report. It shows you which tests passed by name and has a small summary at the end.
+
+### junit
+
+This reporter outputs the standard junit spec in xml format.
+
+### progress
+
+This reporter is very condensed and gives you a `.`(pass), `f`(fail), or `*`(skip) character per test and a small summary at the end.
+
+### json-rspec
+
+This reporter includes all information from the rspec runner. Unlike the json reporter this includes rspec specific details.
+
+### html
+
+This renders html code to view your tests in a browser. It includes all the test and summary information.

data/docs/resources/aide_conf.md.erb

@@ -34,7 +34,7 @@ Use the where clause to match a selection_line to one rule or a particular set o
 
 <br>
 
-## Supported Properties
+## Properties
 
 * `conf_path`, `content`, `rules`, `all_have_rule`
 

data/docs/resources/apache.md.erb

@@ -25,7 +25,7 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
 * 'service', 'conf_dir', 'conf_path', 'user'
 

data/docs/resources/auditd_conf.md.erb

@@ -24,7 +24,7 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
 This matcher will match any property listed in the `auditd.conf` configuration file. Property names and expected values are case-insensitive:
 

data/docs/resources/bash.md.erb

@@ -33,7 +33,7 @@ For example:
 
 <br>
 
-## Supported Properties
+## Properties
 
 * `exit_status`, `stderr`, `stdout`
 

data/docs/resources/bridge.md.erb

@@ -19,7 +19,7 @@ A `bridge` resource block declares the bridge to be tested and what interface it
 
 <br>
 
-## Supported Properties 
+## Properties 
 
 * On Linux platforms, any value in the `/sys/class/net/{interface}/bridge` directory may be tested
 * On the Windows platform, the `Get-NetAdapter` cmdlet is associated with the `Get-NetAdapterBinding` cmdlet and returns the `ComponentID ms_bridge` value as a JSON object

data/docs/resources/bsd_service.md.erb

@@ -37,7 +37,7 @@ The path to the service manager's control may be specified for situations where
 
 <br>
 
-## Supported Properties
+## Properties
 
 All properties available to the `service` resource may be used.
 <br>

data/docs/resources/cpan.md.erb

@@ -23,7 +23,7 @@ where
 
 <br>
 
-## Supported Resource Parameters
+## Resource Parameters
 
 This resource uses package names and perl library paths as resource parameters.
 

data/docs/resources/cran.md.erb

@@ -23,7 +23,7 @@ where
 
 <br>
 
-## Resource Parameter Examples
+## Examples
 
 The following examples show how to use this InSpec audit resource.
 

data/docs/resources/crontab.md.erb

@@ -18,7 +18,7 @@ A `crontab` resource block declares a user (which defaults to the current user,
 
 <br>
 
-## Resource Parameter Examples
+## Examples
 
 The following examples show how to use this InSpec audit resource.
 

data/docs/resources/csv.md.erb

@@ -24,7 +24,7 @@ where
 
 <br>
 
-## Resource Parameter Examples
+## Examples
 
 The following examples show how to use this InSpec audit resource.
 

data/docs/resources/dh_params.md.erb

@@ -36,7 +36,7 @@ Verify whether file contains DH parameters:
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
 generator, modulus, prime_length, pem, text
 

data/docs/resources/directory.md.erb

@@ -18,7 +18,7 @@ A `directory` resource block declares the location of the directory to be tested
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
 All of the properties available to `file` may be used with `directory`.
 

data/docs/resources/docker_container.md.erb

@@ -25,7 +25,7 @@ A `docker_container` resource block declares the configuration data to be tested
 
 ## Resource Parameter Examples 
 
-### container
+### name
 
 The container name can also be passed with the `name` resource parameter:
 
@@ -34,6 +34,8 @@ The container name can also be passed with the `name` resource parameter:
       it { should be_running }
     end
 
+### id
+
 Alternatively, you can pass in the container id:
 
     describe docker_container(id: '71b5df59442b') do

data/docs/resources/elasticsearch.md.erb

@@ -40,7 +40,7 @@ To simply check if nodes exist that match the criteria, use the `exist` matcher:
       it { should exist }
     end
 
-## Supported Resource Properties
+## Properties
 
 The following properties are provided:
 

data/docs/resources/etc_fstab.md.erb

@@ -35,7 +35,7 @@ Use the optional constructor parameter to give an alternative path to fstab file
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
 * `device_name` is the name associated with the device.
 * `mount_point` is the directory at which the filesystem is configured to be mounted.

data/docs/resources/etc_group.md.erb

@@ -32,13 +32,13 @@ where
     * `name: 'name'`, `group_name: 'group_name'`, `password: 'password'`, `gid: 'gid'`, `group_id: 'gid'`, `users: 'user_name'`, `members: 'member_name'`
 <br>
 
-## Supported Resource parameters
+## Properties
 
 * `'gids'`, `'groups'`, and `'users'` are valid resource parameters for this resource.
 
 <br>
 
-## Resource Parameter Examples
+## Examples
 
 The following examples show how to use this InSpec audit resource.
 

data/docs/resources/etc_hosts.md.erb

@@ -38,7 +38,7 @@ where
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
     'ip_address', 'primary_name', 'all_host_names'
 

data/docs/resources/etc_hosts_allow.md.erb

@@ -34,7 +34,7 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
     'daemon', 'client_list', 'options'
 

data/docs/resources/etc_hosts_deny.md.erb

@@ -34,13 +34,13 @@ where
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
     'daemon', 'client_list', 'options'
 
 <br>
 
-## Parameter Examples and Return Types
+## Parameter Examples
 
 ### daemon
 

data/docs/resources/file.md.erb

@@ -24,17 +24,17 @@ where
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
-### General Resource Properties
+### General Properties
 
 content, size, basename, path, owner, group, type 
 
-### Unix/Linux Resource Properties 
+### Unix/Linux Properties 
 
 symlink, mode, link_path, mtime, size, selinux\_label, md5sum, sha256sum, path, source, source\_path, uid, gid
 
-### Windows Resource Properties
+### Windows Properties
 
 file\_version, product\_version
 

data/docs/resources/firewalld.md.erb

@@ -29,7 +29,7 @@ Use the where clause to test open interfaces, sources, and services in active zo
     
 <br>
 
-## Supported Properties
+## Properties
 
 ### interfaces
 

data/docs/resources/http.md.erb

@@ -49,7 +49,7 @@ Beginning with InSpec 1.41, you can enable the ability to have the HTTP test exe
 In InSpec 2.0, the HTTP test will automatically execute remotely whenever InSpec is testing a remote node.
 
 <br>
-## Supported Resource Properties
+## Properties
 
 body, headers, http_method, status,
 

data/docs/resources/iis_app.md.erb

@@ -42,7 +42,7 @@ For example:
 
 <br>
 
-## Supported Resource Properties
+## Properties
 application\_pool, path, physical\_path, protocols, site\_name
 
 <br>

data/docs/resources/iis_site.md.erb

@@ -40,7 +40,7 @@ For example:
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
 app\_pool, bindings, path, state
 

data/docs/resources/inetd_conf.md.erb

@@ -24,7 +24,7 @@ where
 
 <br>
 
-## Supported Resource Properties
+## Properties
 
 This resource supports any of the properties listed as services in the `inetd.conf` file. You may want to ensure that specific services do not listen via `inetd.conf`.
 

data/docs/resources/ini.md.erb

@@ -43,7 +43,7 @@ In the event a section or setting name has a period in it, the alternate syntax
     its(['section.with.a.dot.in.it', 'setting.name.with.dots']) { should cmp 'lotsadots' }
 
 <br>
-## Supported Properties
+## Properties
 
 This resource supports any of the settings listed in an INI file as properties. 
 

data/docs/resources/interface.md.erb

@@ -22,7 +22,7 @@ An `interface` resource block declares network interface properties to be tested
     end
 
 <br>
-## Resource Properties
+## Properties
 
 `name`, `speed`
 <br>

data/docs/resources/kernel_parameter.md.erb

@@ -1,11 +1,12 @@
 ---
 title: About the kernel_parameter Resource
+os: Linux
 ---
 
 # kernel_parameter
 
 Use the `kernel_parameter` InSpec audit resource to test kernel parameters on Linux platforms.
-
+ These parameters are located under `/proc/cmdline`. 
 <br>
 
 ## Syntax
@@ -42,7 +43,7 @@ The following examples show how to use this InSpec audit resource.
 ### Test if an IPv6 address accepts redirects
 
     describe kernel_parameter('net.ipv6.conf.interface.accept_redirects') do
-      its('value') { should eq 'true' }
+      its('value') { should cmp 'true' }
     end
 
 <br>
@@ -50,9 +51,3 @@ The following examples show how to use this InSpec audit resource.
 ## Matchers
 
 For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
-
-### value
-
-The `value` matcher tests the value assigned to the named IP address versus the value declared in the test:
-
-    its('value') { should eq 0 }

data/docs/resources/key_rsa.md.erb

@@ -1,5 +1,6 @@
 ---
 title: The key_rsa Resource
+os: Linux
 ---
 
 # key_rsa
@@ -29,15 +30,13 @@ You can use an optional passphrase with `key_rsa`
 
 <br>
 
-## Supported Properties
+## Properties
 
-### public?
+  * `public_key`, `private_key`, `key_length`
 
-To verify if a key is public use the following:
+<br>
 
-    describe key_rsa('/etc/pki/www.mywebsite.com.key') do
-      it { should be_public }
-    end
+## Property Examples
 
 ### public_key (String)
 
@@ -47,15 +46,6 @@ The `public_key` property returns the public part of the RSA key pair
       its('public_key') { should match "-----BEGIN PUBLIC KEY-----\n3597459df9f3982......" }
     end
 
-### private?
-
-This property verifies that the key includes a private key:
-
-    describe key_rsa('/etc/pki/www.mywebsite.com.key') do
-      it { should be_private }
-    end
-
-
 ### private_key (String)
 
 The `private_key` property returns the private key or the RSA key pair.
@@ -71,3 +61,23 @@ The `key_length` property allows testing the number of bits in the key pair.
     describe key_rsa('/etc/pki/www.mywebsite.com.key') do
       its('key_length') { should eq 2048 }
     end
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+
+### public?
+
+To verify if a key is public use the following:
+
+    describe key_rsa('/etc/pki/www.mywebsite.com.key') do
+      it { should be_public }
+    end
+
+### private?
+
+This property verifies that the key includes a private key:
+
+    describe key_rsa('/etc/pki/www.mywebsite.com.key') do
+      it { should be_private }
+    end

data/docs/resources/limits_conf.md.erb

@@ -1,10 +1,11 @@
 ---
 title: About the limits_conf Resource
+os: Linux
 ---
 
 # limits_conf
 
-Use the `limits_conf` InSpec audit resource to test configuration settings in the `/etc/security/limits.conf` file. The `limits.conf` defines limits for processes (by user and/or group names) and helps ensure that the system on which those processes are running remains stable. Each process may be assigned a hard or soft limit.
+Use the `limits_conf` InSpec audit resource to test configuration settings in the `/etc/security/limits.conf` file. The `limits.conf` defines limits for processes (by user and/or group names) and helps ensure that the system running those processes remains stable. Each process may be assigned a hard or soft limit.
 
 * Soft limits are maintained by the shell and defines the number of file handles (or open files) available to the user or group after login
 * Hard limits are maintained by the kernel and defines the maximum number of allowed file handles
@@ -38,10 +39,24 @@ where
 
 <br>
 
+## Properties
+
+* `domain`
+
 ## Examples
 
 The following examples show how to use this InSpec audit resource.
 
+### domain
+
+The `domain` property tests the domain in the `limits.conf` file, along with associated type, item, and value:
+
+    its('domain') { should include ['type', 'item', 'value'] }
+`
+For example:
+
+    its('grantmc') { should include ['hard', 'nofile', '63536'] }
+
 ### Test limits
 
     describe limits_conf('path') do
@@ -55,12 +70,4 @@ The following examples show how to use this InSpec audit resource.
 
 For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
 
-### domain
 
-The `domain` matcher tests the domain in the `limits.conf` file, along with associated type, item, and value:
-
-    its('domain') { should include ['type', 'item', 'value'] }
-`
-For example:
-
-    its('grantmc') { should include ['hard', 'nofile', '63536'] }

data/docs/resources/login_def.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the login_defs Resource
+os: Linux
 ---
 
 # login_defs
@@ -23,10 +24,22 @@ where
 
 <br>
 
+## Properties
+
+This resource supports the properties found in the `login.defs` configuration settings.
+
+<br>
+
 ## Examples
 
 The following examples show how to use this InSpec audit resource.
 
+### name
+
+The `name` matcher tests the value of `name` as read from `login.defs` versus the value declared in the test:
+
+    its('name') { should eq 'foo' }
+
 ### Test password expiration settings
 
     describe login_defs do
@@ -55,8 +68,4 @@ The following examples show how to use this InSpec audit resource.
 
 For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
 
-### name
 
-The `name` matcher tests the value of `name` as read from `login.defs` versus the value declared in the test:
-
-    its('name') { should eq 'foo' }

data/docs/resources/nginx.md.erb

@@ -29,13 +29,13 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
 * 'compiler_info',  'error_log_path',  'http_client_body_temp_path',  'http_fastcgi_temp_path',  'http_log_path',  'http_proxy_temp_path',  'http_scgi_temp_path',  'http_uwsgi_temp_path',  'lock_path',  'modules', 'modules_path',  'openssl_version',  'prefix',  'sbin_path',  'service',  'support_info',  'version'
 
 <br>
 
-## Property Examples and Return Types
+## Property Examples
 
 ### version(String)
 

data/docs/resources/postgres_hba_conf.md.erb

@@ -24,13 +24,13 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
     'address', 'auth_method', 'auth_params', 'conf_dir' , 'conf_file' , 'database', 'params' ,'type', 'user'
 
 <br>
 
-## Property Examples and Return Types
+## Property Examples
 
 ### address([String])
 

data/docs/resources/postgres_ident_conf.md.erb

@@ -24,13 +24,13 @@ where
 
 <br>
 
-## Supported Properties
+## Properties
 
     'conf_file', 'map_name', 'params', 'pg_username', 'system_username'
 
 <br>
 
-## Property Examples and Return Types
+## Property Examples
 
 ### map_name([String])
 

data/docs/resources/user.md.erb

@@ -40,7 +40,6 @@ The following examples show how to use this InSpec audit resource.
 
     describe user('root') do
       it { should exist }
-      it { should belong_to_group 'root' }
       its('uid') { should eq 0 }
       its('groups') { should eq ['root'] }
     end
@@ -64,7 +63,7 @@ The `nginx` user is typically `www-data`, but on CentOS it's `nginx`. The follow
 
 ## Matchers
 
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
 
 ### exist
 
@@ -76,7 +75,7 @@ The `exist` matcher tests if the named user exists:
 
 The `gid` matcher tests the group identifier:
 
-    its('gid') { should eq 1234 } }
+    its('gid') { should eq 1234 }
 
 where `1234` represents the user identifier.
 
@@ -92,7 +91,7 @@ where `root` represents the group.
 
 The `groups` matcher tests two (or more) groups to which the user belongs:
 
-    its('groups') { should eq ['root', 'other']}
+    its('groups') { should eq ['root', 'other'] }
 
 ### home
 
@@ -126,7 +125,7 @@ The `shell` matcher tests the path to the default shell for the user:
 
 The `uid` matcher tests the user identifier:
 
-    its('uid') { should eq 1234 } }
+    its('uid') { should eq 1234 }
 
 where `1234` represents the user identifier.
 

data/docs/resources/x509_certificate.md.erb

@@ -24,7 +24,7 @@ An `x509_certificate` resource block declares a certificate `key file` to be tes
 
 <br>
 
-## Supported Properties
+## Properties
 
 ### subject.XX
 

data/docs/resources/xml.md.erb

@@ -50,12 +50,12 @@ where
 
 In the above example, you see the use of `@` and `attribute::` which are both methods of fetching attributes.
 
-<br>
-
 In the event the path contains an element which contains periods, the alternate syntax can be used:
 
     its(['root/name.with.a.period']) { should cmp 'so_many_dots' }
 
+<br>
+
 ## Examples
 
 The following examples show how to use this InSpec audit resource.

data/lib/inspec/base_cli.rb

@@ -93,11 +93,19 @@ module Inspec
       }
     end
 
-    def self.parse_reporters(opts) # rubocop:disable Metrics/AbcSize
+    def self.parse_reporters(opts) # rubocop:disable Metrics/AbcSize, Metrics/CyclomaticComplexity, Metrics/PerceivedComplexity
       # merge in any legacy formats as reporter
       # this method will only be used for ad-hoc runners
       if !opts['format'].nil? && opts['reporter'].nil?
         warn '[DEPRECATED] The option --format is being is being deprecated and will be removed in inspec 3.0. Please use --reporter'
+
+        # see if we are using the legacy output to write to files
+        if opts['output']
+          warn '[DEPRECATED] The option \'output\' is being is being deprecated and will be removed in inspec 3.0. Please use --reporter name:path'
+          opts['format'] = "#{opts['format']}:#{opts['output']}"
+          opts.delete('output')
+        end
+
         opts['reporter'] = Array(opts['format'])
         opts.delete('format')
       end

data/lib/inspec/runner_rspec.rb

@@ -121,12 +121,7 @@ module Inspec
     #
     # @return [nil]
     def configure_output
-      if !@conf['output'] || @conf['output'] == '-'
-        RSpec.configuration.output_stream = $stdout
-      else
-        RSpec.configuration.output_stream = @conf['output']
-      end
-
+      RSpec.configuration.output_stream = $stdout
       @formatter = RSpec.configuration.add_formatter(Inspec::Formatters::Base)
       RSpec.configuration.add_formatter(Inspec::Formatters::ShowProgress, $stderr) if @conf[:show_progress]
       set_optional_formatters

data/lib/inspec/version.rb

@@ -4,5 +4,5 @@
 # author: Christoph Hartmann
 
 module Inspec
-  VERSION = '1.51.18'
+  VERSION = '1.51.21'
 end

data/lib/resources/package.rb

@@ -267,6 +267,12 @@ module Inspec::Resources
         Select-Object -Property DisplayName,DisplayVersion | ConvertTo-Json
       EOF
 
+      # We cannot rely on `exit_status` since PowerShell always exits 0 from the
+      # above command. Instead, if no package is found the output of the command
+      # will be `''` so we can use that to return `{}` to match the behavior of
+      # other package managers.
+      return {} if cmd.stdout == ''
+
       begin
         package = JSON.parse(cmd.stdout)
       rescue JSON::ParserError => e

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: inspec
 version: !ruby/object:Gem::Version
-  version: 1.51.18
+  version: 1.51.21
 platform: ruby
 authors:
 - Dominik Richter
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-02-12 00:00:00.000000000 Z
+date: 2018-02-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: train
@@ -299,6 +299,7 @@ files:
 - docs/migration.md
 - docs/plugin_kitchen_inspec.md
 - docs/profiles.md
+- docs/reporters.md
 - docs/resources/aide_conf.md.erb
 - docs/resources/apache.md.erb
 - docs/resources/apache_conf.md.erb