inspec 1.51.6 → 1.51.15

data/docs/resources/filesystem.md.erb

@@ -1,40 +1,40 @@
----
-title: About the filesystem Resource
----
-
-# filesystem
-
-Use the `filesystem` InSpec resource to audit filesystem disk space usage.
-
-<br>
-
-## Syntax
-
-A `filesystem` resource block declares tests for disk space in a partion:
-
-    describe filesystem('/') do
-      its('size') { should be >= 32000 }
-    end
-
-where
-
-* `filesystem('/')` states that the resource will look at the root (/) partition.
-* `size` is measured in megabytes (MB).
-
-<br>
-
-## Resource Property Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test if the root partition is greater thank 32000 MB
-
-    describe filesystem('/') do
-      its('size') { should be >= 32000 }
-    end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
+---
+title: About the filesystem Resource
+---
+
+# filesystem
+
+Use the `filesystem` InSpec resource to audit filesystem disk space usage.
+
+<br>
+
+## Syntax
+
+A `filesystem` resource block declares tests for disk space in a partion:
+
+    describe filesystem('/') do
+      its('size') { should be >= 32000 }
+    end
+
+where
+
+* `filesystem('/')` states that the resource will look at the root (/) partition.
+* `size` is measured in megabytes (MB).
+
+<br>
+
+## Resource Property Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test if the root partition is greater thank 32000 MB
+
+    describe filesystem('/') do
+      its('size') { should be >= 32000 }
+    end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).

data/docs/resources/firewalld.md.erb

@@ -1,106 +1,106 @@
----
-title: About the firewalld Resource
----
-
-# firewalld
-
-Use the `firewalld` InSpec audit resource to test that firewalld is configured to allow and deny access to specific hosts, services and ports on a system.
-
-A firewalld has a number of zones that can be configured to allow and deny access to specific hosts, services, and ports.
-
-<br>
-
-## Syntax
-
-    describe firewalld do
-      it { should be_running }
-      its('default_zone') { should eq 'public' }
-      it { should have_service_enabled_in_zone('ssh', 'public') }
-      it { should have_rule_enabled('family=ipv4 source address=192.168.0.14 accept', 'public') }
-    end
-
-Use the where clause to test open interfaces, sources, and services in active zones.
-
-    describe firewalld.where { zone == 'public' } do
-      its('interfaces') { should cmp ['enp0s3', 'eno2'] }
-      its('sources') { should cmp ['192.168.1.0/24', '192.168.1.2'] }
-      its('services') { should cmp ['ssh', 'icmp'] }
-    end
-    
-<br>
-
-## Supported Properties
-
-### interfaces
-
-The `interfaces` property is used in conjunction with the where class to display open interfaces in an active zone.
-
-    describe firewalld.where { zone == 'public' } do
-      its('interfaces') { should cmp ['enp0s3', 'eno2'] }
-    end
-
-### sources
-
-The `sources` property is used in conjunction with the where class to display open sources in an active zone.
-
-    describe firewalld.where { zone == 'public' } do
-      its('sources') { should cmp ['192.168.1.0/24', '192.168.1.2'] }
-    end
-
-### services
-
-The `services` property is used in conjunction with the where class to display open services in an active zone.
-
-    describe firewalld.where { zone == 'public' } do
-      its('services') { should cmp ['ssh', 'icmp'] }
-    end
-
-### default_zone
-
-The `default_zone` property displays the default active zone to be used.
-
-    its('default_zone') { should eq 'public' }
-
-<br>
-
-## 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 firewalld service is installed:
-
-    it { should be_installed }
-
-### `be_running`
-
-The `be_running` matcher tests if the firewalld service is running:
-
-    it { should be_running }
-
-### have_zone
-
-`have_zone` returns true or false if the zone is set on firewalld. It does not mean the zone is active.
-
-    it { should have_zone('public') }
-
-### `have_service_enabled_in_zone`
-
-`have_service_enabled_in_zone` returns true or false if the service is allowed in the specified zone.
-
-    it { should have_service_enabled_in_zone('ssh', 'public') }
-
-### `have_port_enabled_in_zone`
-
-`have_port_enabled_in_zone` returns true or false if the port is allowed in the specified zone.
-
-    it { should have_port_enabled_in_zone('22/tcp', 'public') }
-
-### `have_rule_enabled`
-
-`have_rule_enabled` returns true or false if the rich-rule has been specified in the zone.
-
-    it { should have_rule_enabled('family=ipv4 source address=192.168.0.14 accept', 'public') }
-
+---
+title: About the firewalld Resource
+---
+
+# firewalld
+
+Use the `firewalld` InSpec audit resource to test that firewalld is configured to allow and deny access to specific hosts, services and ports on a system.
+
+A firewalld has a number of zones that can be configured to allow and deny access to specific hosts, services, and ports.
+
+<br>
+
+## Syntax
+
+    describe firewalld do
+      it { should be_running }
+      its('default_zone') { should eq 'public' }
+      it { should have_service_enabled_in_zone('ssh', 'public') }
+      it { should have_rule_enabled('family=ipv4 source address=192.168.0.14 accept', 'public') }
+    end
+
+Use the where clause to test open interfaces, sources, and services in active zones.
+
+    describe firewalld.where { zone == 'public' } do
+      its('interfaces') { should cmp ['enp0s3', 'eno2'] }
+      its('sources') { should cmp ['192.168.1.0/24', '192.168.1.2'] }
+      its('services') { should cmp ['ssh', 'icmp'] }
+    end
+    
+<br>
+
+## Supported Properties
+
+### interfaces
+
+The `interfaces` property is used in conjunction with the where class to display open interfaces in an active zone.
+
+    describe firewalld.where { zone == 'public' } do
+      its('interfaces') { should cmp ['enp0s3', 'eno2'] }
+    end
+
+### sources
+
+The `sources` property is used in conjunction with the where class to display open sources in an active zone.
+
+    describe firewalld.where { zone == 'public' } do
+      its('sources') { should cmp ['192.168.1.0/24', '192.168.1.2'] }
+    end
+
+### services
+
+The `services` property is used in conjunction with the where class to display open services in an active zone.
+
+    describe firewalld.where { zone == 'public' } do
+      its('services') { should cmp ['ssh', 'icmp'] }
+    end
+
+### default_zone
+
+The `default_zone` property displays the default active zone to be used.
+
+    its('default_zone') { should eq 'public' }
+
+<br>
+
+## 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 firewalld service is installed:
+
+    it { should be_installed }
+
+### `be_running`
+
+The `be_running` matcher tests if the firewalld service is running:
+
+    it { should be_running }
+
+### have_zone
+
+`have_zone` returns true or false if the zone is set on firewalld. It does not mean the zone is active.
+
+    it { should have_zone('public') }
+
+### `have_service_enabled_in_zone`
+
+`have_service_enabled_in_zone` returns true or false if the service is allowed in the specified zone.
+
+    it { should have_service_enabled_in_zone('ssh', 'public') }
+
+### `have_port_enabled_in_zone`
+
+`have_port_enabled_in_zone` returns true or false if the port is allowed in the specified zone.
+
+    it { should have_port_enabled_in_zone('22/tcp', 'public') }
+
+### `have_rule_enabled`
+
+`have_rule_enabled` returns true or false if the rich-rule has been specified in the zone.
+
+    it { should have_rule_enabled('family=ipv4 source address=192.168.0.14 accept', 'public') }
+
 It is not necessary to add the "rule" string, and you can start with the optional flags that are used in firewalld and end with the action

data/docs/resources/gem.md.erb

@@ -1,78 +1,78 @@
----
-title: About the gem Resource
----
-
-# gem
-
-Use the `gem` InSpec audit resource to test if a global Gem package is installed.
-
-<br>
-
-## Syntax
-
-A `gem` resource block declares a package and (optionally) a package version:
-
-    describe gem('gem_package_name', 'gem_binary') do
-      it { should be_installed }
-    end
-
-where
-
-* `('gem_package_name')` must specify a Gem package, such as `'rubocop'`
-* `('gem_binary')` can specify the path to a non-default gem binary, defaults to `'gem'`
-* `be_installed` is a valid matcher for this resource
-
-<br>
-
-## Resource Property Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Verify that a gem package is installed, with a specific version
-
-    describe gem('rubocop') do
-      it { should be_installed }
-      its('version') { should eq '0.33.0' }
-    end
-
-### Verify that a gem package is not installed
-
-    describe gem('rubocop') do
-      it { should_not be_installed }
-    end
-
-### Verify that a gem package is installed in an omnibus environment
-
-    describe gem('pry', '/opt/ruby-2.3.1/embedded/bin/gem') do
-      it { should be_installed }
-    end
-
-### Verify that a gem package is installed in a chef omnibus environment
-
-    describe gem('chef-sugar', :chef) do
-      it { should be_installed }
-    end
-
-### Verify that a gem package is installed in a chef-server omnibus environment
-
-    describe gem('knife-backup', :chef_server) do
-      it { should be_installed }
-    end
-
-<br>
-
-## 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 Gem package is installed:
-
-    it { should be_installed }
-
-### version
-
-The `version` matcher tests if the named package version is on the system:
-
-    its('version') { should eq '0.33.0' }
+---
+title: About the gem Resource
+---
+
+# gem
+
+Use the `gem` InSpec audit resource to test if a global Gem package is installed.
+
+<br>
+
+## Syntax
+
+A `gem` resource block declares a package and (optionally) a package version:
+
+    describe gem('gem_package_name', 'gem_binary') do
+      it { should be_installed }
+    end
+
+where
+
+* `('gem_package_name')` must specify a Gem package, such as `'rubocop'`
+* `('gem_binary')` can specify the path to a non-default gem binary, defaults to `'gem'`
+* `be_installed` is a valid matcher for this resource
+
+<br>
+
+## Resource Property Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Verify that a gem package is installed, with a specific version
+
+    describe gem('rubocop') do
+      it { should be_installed }
+      its('version') { should eq '0.33.0' }
+    end
+
+### Verify that a gem package is not installed
+
+    describe gem('rubocop') do
+      it { should_not be_installed }
+    end
+
+### Verify that a gem package is installed in an omnibus environment
+
+    describe gem('pry', '/opt/ruby-2.3.1/embedded/bin/gem') do
+      it { should be_installed }
+    end
+
+### Verify that a gem package is installed in a chef omnibus environment
+
+    describe gem('chef-sugar', :chef) do
+      it { should be_installed }
+    end
+
+### Verify that a gem package is installed in a chef-server omnibus environment
+
+    describe gem('knife-backup', :chef_server) do
+      it { should be_installed }
+    end
+
+<br>
+
+## 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 Gem package is installed:
+
+    it { should be_installed }
+
+### version
+
+The `version` matcher tests if the named package version is on the system:
+
+    its('version') { should eq '0.33.0' }

data/docs/resources/group.md.erb

@@ -1,60 +1,60 @@
----
-title: About the group Resource
----
-
-# group
-
-Use the `group` InSpec audit resource to test groups on the system.
-
-<br>
-
-## Syntax
-
-A `group` resource block declares a group, and then the details to be tested, such as if the group is a local group, the group identifier, or if the group exists:
-
-    describe group('group_name') do
-      it { should exist }
-      its('gid') { should eq 0 }
-    end
-
-where
-
-* `'group_name'` must specify the name of a group on the system
-* `exist` and `'gid'` are valid matchers for this resource
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test the group identifier for the root group
-
-    describe group('root') do
-      it { should exist }
-      its('gid') { should eq 0 }
-    end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
-
-### be_local
-
-The `be_local` matcher tests if the group is a local group:
-
-    it { should be_local }
-
-### exist
-
-The `exist` matcher tests if the named user exists:
-
-    it { should exist }
-
-### gid
-
-The `gid` matcher tests the named group identifier:
-
-    its('gid') { should eq 1234 }
+---
+title: About the group Resource
+---
+
+# group
+
+Use the `group` InSpec audit resource to test groups on the system.
+
+<br>
+
+## Syntax
+
+A `group` resource block declares a group, and then the details to be tested, such as if the group is a local group, the group identifier, or if the group exists:
+
+    describe group('group_name') do
+      it { should exist }
+      its('gid') { should eq 0 }
+    end
+
+where
+
+* `'group_name'` must specify the name of a group on the system
+* `exist` and `'gid'` are valid matchers for this resource
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test the group identifier for the root group
+
+    describe group('root') do
+      it { should exist }
+      its('gid') { should eq 0 }
+    end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+
+### be_local
+
+The `be_local` matcher tests if the group is a local group:
+
+    it { should be_local }
+
+### exist
+
+The `exist` matcher tests if the named user exists:
+
+    it { should exist }
+
+### gid
+
+The `gid` matcher tests the named group identifier:
+
+    its('gid') { should eq 1234 }