inspec 1.51.25 → 2.0.16

data/docs/resources/bash.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the bash Resource
+platform: linux
 ---
 
 # bash
@@ -63,7 +64,7 @@ The `stdout` property tests results of the command as returned in standard outpu
 
 ## 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
 

data/docs/resources/bond.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the bond Resource
+platform: linux
 ---
 
 # bond
@@ -73,7 +74,7 @@ The `params` matcher tests arbitrary parameters for the bonded network interface
 
 ## 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
 

data/docs/resources/bridge.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the bridge Resource
+platform: linux
 ---
 
 # bridge
@@ -19,7 +20,7 @@ A `bridge` resource block declares the bridge to be tested and what interface it
 
 <br>
 
-## 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
@@ -36,9 +37,11 @@ The `interfaces` property tests if the named interface is present:
     its('interfaces') { should eq 'bar' }
     its('interfaces') { should include('foo') }
 
+<br>
+
 ## 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
 

data/docs/resources/bsd_service.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the bsd_service Resource
+platform: linux
 ---
 
 # bsd_service
@@ -40,11 +41,12 @@ The path to the service manager's control may be specified for situations where
 ## Properties
 
 All properties available to the `service` resource may be used.
+
 <br>
 
 ## 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/).
 
 ### be_enabled
 

data/docs/resources/command.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the command Resource
+platform: os
 ---
 
 # command
@@ -127,7 +128,7 @@ Wix includes serveral tools -- such as `candle` (preprocesses and compiles sourc
 
 ## 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
 

data/docs/resources/cpan.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the cpan Resource
+platform: linux
 ---
 
 # cpan
@@ -43,7 +44,7 @@ This resource uses package names and perl library paths as resource parameters.
       it { should be_installed }
       its('version') { should eq '3.7.0' }
     end
-    
+
 ### Test if DBD::Pg is installed within a custom PERL5LIB path on the system
 
 Hint: You can pass multiple paths separated with a colon
@@ -69,10 +70,10 @@ The `version` property tests if the named package version is on the system:
 
 ## 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/).
 
 ### be_installed
 
 The `be_installed` matcher tests if the named package is installed on the system:
 
-    it { should be_installed }
+    it { should be_installed }

data/docs/resources/cran.md.erb

@@ -1,12 +1,13 @@
 ---
 title: About the cran Resource
+platform: linux
 ---
 
 # cran
 
 Use the `cran` InSpec audit resource to test R modules that are installed from CRAN package repository.
 
-<br> 
+<br>
 
 ## Syntax
 

data/docs/resources/crontab.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the crontab Resource
+platform: linux
 ---
 
 # crontab
@@ -84,4 +85,4 @@ InSpec will automatically interpret crontab-supported special time strings. For
 
 ## 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/).

data/docs/resources/csv.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the csv Resource
+platform: os
 ---
 
 # csv
@@ -48,6 +49,6 @@ The `name` property tests the value of `name` as read from a CSV file compared t
 
 ## 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/).
 
 

data/docs/resources/dh_params.md.erb

@@ -1,5 +1,6 @@
 ---
 title: The dh_params Resource
+platform: linux
 ---
 
 # dh_params
@@ -198,7 +199,7 @@ Verify via `openssl dhparam` command:
 
 ## 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/).
 
 ### valid?
 

data/docs/resources/directory.md.erb

@@ -1,10 +1,11 @@
 ---
 title: About the directory Resource
+platform: os
 ---
 
 # directory
 
-Use the `directory` InSpec audit resource to test if the file type is a directory. This is equivalent to using the `file` resource and the `be_directory` matcher, but provides a simpler and more direct way to test directories. 
+Use the `directory` InSpec audit resource to test if the file type is a directory. This is equivalent to using the `file` resource and the `be_directory` matcher, but provides a simpler and more direct way to test directories.
 
 <br>
 
@@ -23,6 +24,7 @@ A `directory` resource block declares the location of the directory to be tested
 All of the properties available to `file` may be used with `directory`.
 
 <br>
+
 ## 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/).

data/docs/resources/docker.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the docker Resource
+platform: linux
 ---
 
 # docker
@@ -109,7 +110,7 @@ Or execute the profile directly via URL:
 
 ## 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/).
 
 ### containers
 

data/docs/resources/docker_container.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the docker_container Resource
+platform: linux
 ---
 
 # docker_container
@@ -23,7 +24,9 @@ A `docker_container` resource block declares the configuration data to be tested
       its('command') { should eq 'nc -ll -p 1234 -e /bin/cat' }
     end
 
-## Resource Parameter Examples 
+<br>
+
+## Resource Parameter Examples
 
 ### name
 
@@ -97,5 +100,5 @@ The `command` property tests the value of the container run command:
 
 ## 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/).
 

data/docs/resources/docker_image.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the docker_image Resource
+platform: linux
 ---
 
 # docker_image
@@ -83,7 +84,7 @@ The `tag` property tests the value of image tag:
 
 ## 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
 

data/docs/resources/docker_service.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the docker_service Resource
+platform: linux
 ---
 
 # docker_service
@@ -102,7 +103,7 @@ The `tag` property tests the value of image tag:
 
 ## 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
 

data/docs/resources/elasticsearch.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the Elasticsearch Resource
+platform: linux
 ---
 
 # elasticsearch
@@ -9,12 +10,16 @@ Elasticsearch cluster. InSpec retrieves the node list from the cluster node URL
 provided (defaults to `http://localhost:9200`) and provides the ability to query
 a variety of settings and statuses.
 
+<br>
+
 ## Syntax
 
     describe elasticsearch do
       its('property') { should cmp 'value' }
     end
 
+<br>
+
 ## Supported Resource parameters
 
 The `elasticsearch` resource accepts a number of optional resource parameters:
@@ -40,6 +45,8 @@ To simply check if nodes exist that match the criteria, use the `exist` matcher:
       it { should exist }
     end
 
+<br>
+
 ## Properties
 
 The following properties are provided:
@@ -48,6 +55,8 @@ The following properties are provided:
 
 Since the `elasticsearch` resource is meant for use on a cluster, each property will return an array of the values for each node that matches any provided search criteria. Using InSpec's `cmp` matcher helps avoid issues when comparing values when there is only a single match (i.e. when the cluster only contains a single node, or the `where` filter criteria provided only returns a single node).
 
+<br>
+
 ## Property Examples
 
 ### build_hash
@@ -226,6 +235,8 @@ Returns the version of Elasticsearch running on each node of the cluster.
       its('version') { should cmp '5.5.2' }
     end
 
+<br>
+
 ## 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/).

data/docs/resources/etc_fstab.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the etc_fstab Resource
+platform: linux
 ---
 
 # etc_fstab
@@ -121,4 +122,4 @@ Use the optional constructor parameter to give an alternative path to fstab file
 
 ## 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/).

data/docs/resources/etc_group.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the etc_group Resource
+platform: linux
 ---
 
 # etc_group
@@ -70,5 +71,5 @@ 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/). 
+For a full list of available matchers, please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
 

data/docs/resources/etc_hosts.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the etc_hosts Resource
+platform: linux
 ---
 
 # etc_hosts
@@ -70,6 +71,8 @@ where
       its('all_host_names') { should eq [['localhost', 'localhost.localdomain', 'localhost4', 'localhost4.localdomain4'],  ['localhost', 'localhost.localdomain', 'localhost6', 'localhost6.localdomain6']] }
     end
 
+<br>
+
 ## 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/).

data/docs/resources/etc_hosts_allow.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the etc_hosts_allow Resource
+platform: linux
 ---
 
 # etc\_hosts\_allow
@@ -70,4 +71,4 @@ where
 
 ## 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/).

data/docs/resources/etc_hosts_deny.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the etc_hosts_deny Resource
+platform: linux
 ---
 
 # etc\_hosts\_deny
@@ -70,4 +71,4 @@ where
 
 ## 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/).

data/docs/resources/file.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the file Resource
+platform: os
 ---
 
 # file
@@ -28,9 +29,9 @@ where
 
 ### General Properties
 
-content, size, basename, path, owner, group, type 
+content, size, basename, path, owner, group, type
 
-### Unix/Linux Properties 
+### Unix/Linux Properties
 
 symlink, mode, link_path, mtime, size, selinux\_label, md5sum, sha256sum, path, source, source\_path, uid, gid
 
@@ -38,6 +39,8 @@ symlink, mode, link_path, mtime, size, selinux\_label, md5sum, sha256sum, path,
 
 file\_version, product\_version
 
+<br>
+
 ## Resource Property Examples
 
 ### content
@@ -325,7 +328,7 @@ For example, for the following symlink:
 
 ## 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/).
 
 ### be\_allowed
 

data/docs/resources/filesystem.md.erb

@@ -1,5 +1,6 @@
 ---
 title: About the filesystem Resource
+platform: linux
 ---
 
 # filesystem
@@ -37,4 +38,4 @@ 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/).
+For a full list of available matchers, please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).