inspec 1.51.15 → 1.51.18

data/docs/resources/json.md.erb

@@ -1,61 +1,61 @@
----
-title: About the json Resource
----
-
-# json
-
-Use the `json` InSpec audit resource to test data in a JSON file.
-
-<br>
-
-## Syntax
-
-A `json` resource block declares the data to be tested. Assume the following JSON file:
-
-    {
-      "name" : "hello",
-      "meta" : {
-        "creator" : "John Doe"
-      },
-      "array": [
-        "zero",
-        "one"
-      ]
-    }
-
-This file can be queried using:
-
-    describe json('/path/to/name.json') do
-      its('name') { should eq 'hello' }
-      its(['meta','creator']) { should eq 'John Doe' }
-      its(['array', 1]) { should eq 'one' }
-    end
-
-where
-
-* `name` is a configuration setting in a JSON file
-* `should eq 'foo'` tests a value of `name` as read from a JSON file versus the value declared in the test
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test a cookbook version in a policyfile.lock.json file
-
-    describe json('policyfile.lock.json') do
-      its(['cookbook_locks', 'omnibus', 'version']) { should eq('2.2.0') }
-    end
-
-<br>
-
-## Matchers
-
-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 a JSON file versus the value declared in the test:
-
-    its('name') { should eq 'foo' }
+---
+title: About the json Resource
+---
+
+# json
+
+Use the `json` InSpec audit resource to test data in a JSON file.
+
+<br>
+
+## Syntax
+
+A `json` resource block declares the data to be tested. Assume the following JSON file:
+
+    {
+      "name" : "hello",
+      "meta" : {
+        "creator" : "John Doe"
+      },
+      "array": [
+        "zero",
+        "one"
+      ]
+    }
+
+This file can be queried using:
+
+    describe json('/path/to/name.json') do
+      its('name') { should eq 'hello' }
+      its(['meta','creator']) { should eq 'John Doe' }
+      its(['array', 1]) { should eq 'one' }
+    end
+
+where
+
+* `name` is a configuration setting in a JSON file
+* `should eq 'foo'` tests a value of `name` as read from a JSON file versus the value declared in the test
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test a cookbook version in a policyfile.lock.json file
+
+    describe json('policyfile.lock.json') do
+      its(['cookbook_locks', 'omnibus', 'version']) { should eq('2.2.0') }
+    end
+
+<br>
+
+## Matchers
+
+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 a JSON file versus the value declared in the test:
+
+    its('name') { should eq 'foo' }

data/docs/resources/kernel_module.md.erb

@@ -1,106 +1,106 @@
----
-title: About the kernel_module Resource
----
-
-# kernel_module
-
-Use the `kernel_module` InSpec audit resource to test kernel modules on Linux
-platforms. These parameters are located under `/lib/modules`. Any submodule may
-be tested using this resource.
-
-The `kernel_module` resource can also verify if a kernel module is `blacklisted`
-or if a module is disabled via a fake install using the `bin_true` or `bin_false`
-method.
-
-<br>
-
-## Syntax
-
-A `kernel_module` resource block declares a module name, and then tests if that
-module is a loadable kernel module, if it is enabled, disabled or if it is
-blacklisted:
-
-    describe kernel_module('module_name') do
-      it { should be_loaded }
-      it { should_not be_disabled }
-      it { should_not be_blacklisted }
-    end
-
-where
-
-* `'module_name'` must specify a kernel module, such as `'bridge'`
-* `{ should be_loaded }` tests if the module is a loadable kernel module
-* `{ should be_blacklisted }` tests if the module is blacklisted or if the module is disabled via a fake install using /bin/false or /bin/true
-* `{ should be_disabled }` tests if the module is disabled via a fake install using /bin/false or /bin/true
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test a modules 'version'
-
-      describe kernel_module('bridge') do
-        it { should be_loaded }
-        its(:version) { should cmp >= '2.2.2' }
-      end
-
-### Test if a module is loaded, not disabled and not blacklisted
-
-      describe kernel_module('video') do
-        it { should be_loaded }
-        it { should_not be_disabled }
-        it { should_not be_blacklisted }
-      end
-
-### Check if a module is blacklisted
-
-      describe kernel_module('floppy') do
-        it { should be_blacklisted }
-      end
-
-### Ensure a module is *not* blacklisted and it is loaded
-
-      describe kernel_module('video') do
-        it { should_not be_blacklisted }
-        it { should be_loaded }
-      end
-
-### Ensure a module is disabled via 'bin_false'
-
-      describe kernel_module('sstfb') do
-        it { should_not be_loaded }
-        it { should be_disabled }
-      end
-
-### Ensure a module is 'blacklisted'/'disabled' via 'bin_true'
-
-      describe kernel_module('nvidiafb') do
-        it { should_not be_loaded }
-        it { should be_blacklisted }
-      end
-
-### Ensure a module is not loaded
-
-      describe kernel_module('dhcp') do
-        it { should_not be_loaded }
-      end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
-
-### be_loaded
-
-The `be_loaded` matcher tests if the module is a loadable kernel module:
-
-    it { should be_loaded }
-
-### version
-
-The `version` matcher tests if the named module version is on the system:
-
-    its(:version) { should eq '3.2.2' }
+---
+title: About the kernel_module Resource
+---
+
+# kernel_module
+
+Use the `kernel_module` InSpec audit resource to test kernel modules on Linux
+platforms. These parameters are located under `/lib/modules`. Any submodule may
+be tested using this resource.
+
+The `kernel_module` resource can also verify if a kernel module is `blacklisted`
+or if a module is disabled via a fake install using the `bin_true` or `bin_false`
+method.
+
+<br>
+
+## Syntax
+
+A `kernel_module` resource block declares a module name, and then tests if that
+module is a loadable kernel module, if it is enabled, disabled or if it is
+blacklisted:
+
+    describe kernel_module('module_name') do
+      it { should be_loaded }
+      it { should_not be_disabled }
+      it { should_not be_blacklisted }
+    end
+
+where
+
+* `'module_name'` must specify a kernel module, such as `'bridge'`
+* `{ should be_loaded }` tests if the module is a loadable kernel module
+* `{ should be_blacklisted }` tests if the module is blacklisted or if the module is disabled via a fake install using /bin/false or /bin/true
+* `{ should be_disabled }` tests if the module is disabled via a fake install using /bin/false or /bin/true
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test a modules 'version'
+
+      describe kernel_module('bridge') do
+        it { should be_loaded }
+        its(:version) { should cmp >= '2.2.2' }
+      end
+
+### Test if a module is loaded, not disabled and not blacklisted
+
+      describe kernel_module('video') do
+        it { should be_loaded }
+        it { should_not be_disabled }
+        it { should_not be_blacklisted }
+      end
+
+### Check if a module is blacklisted
+
+      describe kernel_module('floppy') do
+        it { should be_blacklisted }
+      end
+
+### Ensure a module is *not* blacklisted and it is loaded
+
+      describe kernel_module('video') do
+        it { should_not be_blacklisted }
+        it { should be_loaded }
+      end
+
+### Ensure a module is disabled via 'bin_false'
+
+      describe kernel_module('sstfb') do
+        it { should_not be_loaded }
+        it { should be_disabled }
+      end
+
+### Ensure a module is 'blacklisted'/'disabled' via 'bin_true'
+
+      describe kernel_module('nvidiafb') do
+        it { should_not be_loaded }
+        it { should be_blacklisted }
+      end
+
+### Ensure a module is not loaded
+
+      describe kernel_module('dhcp') do
+        it { should_not be_loaded }
+      end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+
+### be_loaded
+
+The `be_loaded` matcher tests if the module is a loadable kernel module:
+
+    it { should be_loaded }
+
+### version
+
+The `version` matcher tests if the named module version is on the system:
+
+    its(:version) { should eq '3.2.2' }

data/docs/resources/kernel_parameter.md.erb

@@ -1,58 +1,58 @@
----
-title: About the kernel_parameter Resource
----
-
-# kernel_parameter
-
-Use the `kernel_parameter` InSpec audit resource to test kernel parameters on Linux platforms.
-
-<br>
-
-## Syntax
-
-A `kernel_parameter` resource block declares a parameter and then a value to be tested:
-
-    describe kernel_parameter('path.to.parameter') do
-      its('value') { should eq 0 }
-    end
-
-where
-
-* `'kernel.parameter'` must specify a kernel parameter, such as `'net.ipv4.conf.all.forwarding'`
-* `{ should eq 0 }` states the value to be tested
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test if global forwarding is enabled for an IPv4 address
-
-    describe kernel_parameter('net.ipv4.conf.all.forwarding') do
-      its('value') { should eq 1 }
-    end
-
-### Test if global forwarding is disabled for an IPv6 address
-
-    describe kernel_parameter('net.ipv6.conf.all.forwarding') do
-      its('value') { should eq 0 }
-    end
-
-### Test if an IPv6 address accepts redirects
-
-    describe kernel_parameter('net.ipv6.conf.interface.accept_redirects') do
-      its('value') { should eq 'true' }
-    end
-
-<br>
-
-## 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 }
+---
+title: About the kernel_parameter Resource
+---
+
+# kernel_parameter
+
+Use the `kernel_parameter` InSpec audit resource to test kernel parameters on Linux platforms.
+
+<br>
+
+## Syntax
+
+A `kernel_parameter` resource block declares a parameter and then a value to be tested:
+
+    describe kernel_parameter('path.to.parameter') do
+      its('value') { should eq 0 }
+    end
+
+where
+
+* `'kernel.parameter'` must specify a kernel parameter, such as `'net.ipv4.conf.all.forwarding'`
+* `{ should eq 0 }` states the value to be tested
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test if global forwarding is enabled for an IPv4 address
+
+    describe kernel_parameter('net.ipv4.conf.all.forwarding') do
+      its('value') { should eq 1 }
+    end
+
+### Test if global forwarding is disabled for an IPv6 address
+
+    describe kernel_parameter('net.ipv6.conf.all.forwarding') do
+      its('value') { should eq 0 }
+    end
+
+### Test if an IPv6 address accepts redirects
+
+    describe kernel_parameter('net.ipv6.conf.interface.accept_redirects') do
+      its('value') { should eq 'true' }
+    end
+
+<br>
+
+## 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 }