inspec 1.8.0 → 1.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b9e7420ad169ccfbbc41d2c3228ae4a4b1c0a4e8
-  data.tar.gz: bdfcc40cedc98aa75bca9cfc8625e4206e491003
+  metadata.gz: 1f94253412c3c460db42fc5f03154c96a51a4c7b
+  data.tar.gz: 460e9aa3231989faa7af89b29cc51d4f2a518eb0
 SHA512:
-  metadata.gz: 08855a6d58f7b60a0ddab0a219fedcabf1bb79bec29c296e7002f20671527e018abd1e66c9e720c7d8c736b63ab4732f582e6579a0ba29780a3dadc6c173006c
-  data.tar.gz: f38a61a25c35899a5761ed90ef52d0093bf6ed40ad8226315f9a12b0878d4f0eac8b96af6e1815c63f15d497d3a7646dd54ef7ecfd713d833547bfcee64aba8b
+  metadata.gz: cb44eed7117103ec33fb7ed1f69f236637798124533f1daa2fc0039f86871599d47d1e67506abd904ab3915cb9a6f8078caafdb78465da9ad6c4845f311a08ab
+  data.tar.gz: c10829d5c72a263cbf7794a2e8617a5aae54765de056226604527d3a5dd1217b04006f449da51b11325f2113b4949ca12dc6f6c70b887facc0e935e317aa1ad7

data/CHANGELOG.md

@@ -1,7 +1,45 @@
 # Change Log
 
-## [1.8.0](https://github.com/chef/inspec/tree/1.8.0) (2016-12-16)
-[Full Changelog](https://github.com/chef/inspec/compare/v1.7.2...1.8.0)
+## [1.9.0](https://github.com/chef/inspec/tree/1.9.0) (2017-01-06)
+[Full Changelog](https://github.com/chef/inspec/compare/v1.8.0...1.9.0)
+
+**Implemented enhancements:**
+
+- Optimize regular expression for postgres config parsing [\#1395](https://github.com/chef/inspec/pull/1395) ([chris-rock](https://github.com/chris-rock))
+- print name for supermarket profiles [\#1376](https://github.com/chef/inspec/pull/1376) ([chris-rock](https://github.com/chris-rock))
+- call ssh cookbook from prepare cookbook [\#1369](https://github.com/chef/inspec/pull/1369) ([chris-rock](https://github.com/chris-rock))
+- display if inspec version is outdated [\#1365](https://github.com/chef/inspec/pull/1365) ([chris-rock](https://github.com/chris-rock))
+
+**Fixed bugs:**
+
+- profile upload fails to compliance server [\#1298](https://github.com/chef/inspec/issues/1298)
+- undefined method `max\_connections' for PostgreSQL [\#825](https://github.com/chef/inspec/issues/825)
+- bugfix: expose postgres\_conf parameters via `its` [\#826](https://github.com/chef/inspec/pull/826) ([arlimus](https://github.com/arlimus))
+
+**Closed issues:**
+
+- Yum.repo should show correct name [\#1390](https://github.com/chef/inspec/issues/1390)
+- The 'package' resource is broken in OSX \(with brew as package manager\) [\#1386](https://github.com/chef/inspec/issues/1386)
+- JUnit XML dumping fails [\#1383](https://github.com/chef/inspec/issues/1383)
+- json.rb produces stacktrace when a target file is unreadable [\#1382](https://github.com/chef/inspec/issues/1382)
+- Document Serverspec Migration [\#804](https://github.com/chef/inspec/issues/804)
+
+**Merged pull requests:**
+
+- Download InSpec profiles from Chef Compliance [\#1402](https://github.com/chef/inspec/pull/1402) ([chris-rock](https://github.com/chris-rock))
+- Yum.repo should show correct name [\#1391](https://github.com/chef/inspec/pull/1391) ([Wing924](https://github.com/Wing924))
+- fixes brew json parsing [\#1389](https://github.com/chef/inspec/pull/1389) ([chris-rock](https://github.com/chris-rock))
+- Fix wrong description for the Solaris cases in the unit tests of the 'package' resource [\#1388](https://github.com/chef/inspec/pull/1388) ([jvrplmlmn](https://github.com/jvrplmlmn))
+- Unit test the 'package' resource for OSX \(with brew\) [\#1387](https://github.com/chef/inspec/pull/1387) ([jvrplmlmn](https://github.com/jvrplmlmn))
+- drop ruby 1.9.3 [\#1384](https://github.com/chef/inspec/pull/1384) ([chris-rock](https://github.com/chris-rock))
+- Make "permission denied" condition match that of Train [\#1381](https://github.com/chef/inspec/pull/1381) ([makotots](https://github.com/makotots))
+- mention inspec vendor for compliance dependency [\#1380](https://github.com/chef/inspec/pull/1380) ([alexpop](https://github.com/alexpop))
+- control and lib\_eval\_context unit tests [\#1373](https://github.com/chef/inspec/pull/1373) ([jeremymv2](https://github.com/jeremymv2))
+- Fix Learn Chef tutorial link [\#1372](https://github.com/chef/inspec/pull/1372) ([tpetchel](https://github.com/tpetchel))
+- add guidance for Serverspec migration [\#1368](https://github.com/chef/inspec/pull/1368) ([chris-rock](https://github.com/chris-rock))
+
+## [v1.8.0](https://github.com/chef/inspec/tree/v1.8.0) (2016-12-16)
+[Full Changelog](https://github.com/chef/inspec/compare/v1.7.2...v1.8.0)
 
 **Fixed bugs:**
 

data/Gemfile

@@ -2,13 +2,6 @@
 source 'https://rubygems.org'
 gemspec
 
-# pin dependency for Ruby 1.9.3 since bundler is not
-# detecting that net-ssh 3 does not work with 1.9.3
-if Gem::Version.new(RUBY_VERSION) <= Gem::Version.new('1.9.3')
-  gem 'net-ssh', '~> 2.9'
-  gem 'tins', '~> 1.6.0'
-end
-
 if Gem::Version.new(RUBY_VERSION) < Gem::Version.new('2.2.2')
   gem 'json', '~> 1.8'
   gem 'rack', '< 2.0'

data/docs/migration.md

@@ -0,0 +1,232 @@
+---
+title: InSpec Migration Guide
+---
+
+# Migrate from Serverspec to InSpec
+
+## How is InSpec different from Serverspec
+
+We've written a complete blog post about that topic: [The Road to InSpec](https://blog.chef.io/2015/11/04/the-road-to-inspec/)
+
+## Is InSpec suitable for infrastructure testing?
+
+InSpec is a framework that allows you to run infrastructure testing as well as compliance testing. The compliance features are always optional and provide customers a way to use InSpec for both use-cases. To ensure we build the best infrastructure testing, we migrate our cookbooks [chef-cookbooks](https://github.com/chef-cookbooks) to InSpec.
+
+## Which Serverspec resources are available in InSpec?
+
+The following resources are available in InSpec:
+
+[`bond`](http://inspec.io/docs/reference/resources/bond/), [`bridge`](http://inspec.io/docs/reference/resources/bridge/), [`command`](http://inspec.io/docs/reference/resources/command/), [`file`](http://inspec.io/docs/reference/resources/file/), [`group`](http://inspec.io/docs/reference/resources/group/), [`host`](http://inspec.io/docs/reference/resources/host/), [`interface`](http://inspec.io/docs/reference/resources/interface/), [`iis_website`](http://inspec.io/docs/reference/resources/iis_site/), [`iptables`](http://inspec.io/docs/reference/resources/iptables/), [`kernel_module`](http://inspec.io/docs/reference/resources/kernel_module/), [`linux_kernel_parameter`](http://inspec.io/docs/reference/resources/kernel_parameter/), [`mysql_config`](http://inspec.io/docs/reference/resources/mysql_config/), [`package`](http://inspec.io/docs/reference/resources/package/), [`port`](http://inspec.io/docs/reference/resources/port/), [`ppa`](http://inspec.io/docs/reference/resources/ppa/), [`process`](http://inspec.io/docs/reference/resources/process/), [`service`](http://inspec.io/docs/reference/resources/service/), [`user`](http://inspec.io/docs/reference/resources/user/), [`windows_feature`](http://inspec.io/docs/reference/resources/windows_feature/), [`windows_registry_key`](http://inspec.io/docs/reference/resources/windows_registry_key/), [`yumrepo`](http://inspec.io/docs/reference/resources/yum/)
+
+Some Serverspec resources are not available yet. We implement those resources based on user feedback. If you need a resource that is not available in InSpec, please open an [Github issue](https://github.com/chef/inspec/issues). The list of resources that are not available in InSpec:
+
+`cgroup`, `cron`, `default_gateway`, `docker_container`, `docker_image`, `iis_app_pool`, `ip6tables`, `ipfilter`, `ipnat`, `linux_audit_system`, `lxc`, `mail_alias`, `php_config`, `routing_table`, `selinux`, `selinux_module`, `x509_certificate`, `x509_private_key`, `zfs`
+
+In addition InSpec provides additional [resources](http://inspec.io/docs/reference/resources/) that are not available in Serverspec:
+[`apache_conf`](http://inspec.io/docs/reference/resources/apache_conf/), [`apt`](http://inspec.io/docs/reference/resources/apt/), [`audit_policy`](http://inspec.io/docs/reference/resources/audit_policy/), [`auditd_conf`](http://inspec.io/docs/reference/resources/auditd_conf/), [`bash`](http://inspec.io/docs/reference/resources/bash/), [`csv`](http://inspec.io/docs/reference/resources/csv/), [`etc_shadow`](http://inspec.io/docs/reference/resources/etc_shadow/), [`gem`](http://inspec.io/docs/reference/resources/gem/), [`grub_conf`](http://inspec.io/docs/reference/resources/grub_conf/), [`inetd_conf`](http://inspec.io/docs/reference/resources/inetd_conf/), [`ini`](http://inspec.io/docs/reference/resources/ini/), [`json`](http://inspec.io/docs/reference/resources/json/), [`npm`](http://inspec.io/docs/reference/resources/npm/), [`ntp_conf`](http://inspec.io/docs/reference/resources/ntp_conf/), [`oneget`](http://inspec.io/docs/reference/resources/oneget/), [`pip`](http://inspec.io/docs/reference/resources/pip/), [`powershell`](http://inspec.io/docs/reference/resources/powershell/), [`security_policy`](http://inspec.io/docs/reference/resources/security_policy/), [`ssh_config`](http://inspec.io/docs/reference/resources/ssh_config/), [`sshd_config`](http://inspec.io/docs/reference/resources/sshd_config/), [`sys_info`](http://inspec.io/docs/reference/resources/sys_info/)
+
+## How do I migrate my Serverspec tests to InSpec
+
+For most cases, the migration to InSpec is pretty straight forward. First, replace the current verifier in `kitchen.yml` configuration with:
+
+```
+verifier:
+  name: inspec
+```
+
+Second, rename the directory `test/integration/default/serverspec` to
+`test/integration/default/inspec`
+
+Third, remove the Serverspec-specific code from the test files.
+
+```
+require 'serverspec'
+
+# Required by serverspec
+set :backend, :exec
+```
+
+InSpec is now configured with Test-Kitchen:
+
+```
+kitchen verify package-install-centos-72
+-----> Starting Kitchen (v1.14.2)
+-----> Verifying <package-install-centos-72>...
+       Detected alternative framework tests for `inspec`
+       Loaded  
+
+Target:  ssh://vagrant@127.0.0.1:2200
+
+
+  PHP has
+     ✔  php
+     ✔  the pear.php.net channel
+     ✔  the pecl.php.net channel
+
+Test Summary: 3 successful, 0 failures, 0 skipped
+       Finished verifying <package-install-centos-72> (0m0.40s).
+-----> Kitchen is finished. (0m3.31s)
+```
+
+Some real-world migrations are available:
+
+* [docker](https://github.com/chef-cookbooks/docker)
+* [nginx](https://github.com/chef-cookbooks/chef_nginx/pull/5/files)
+* [mysql](https://github.com/chef-cookbooks/mysql/pull/430/files)
+* [php](https://github.com/chef-cookbooks/php/pull/189/files)
+
+Some general recommendations:
+
+* use test-kitchen 1.14+
+* in case of errors, increase the log level `kitchen verify package-install-centos-72 -l debug`
+
+## Do I still need the backend configuration?
+
+InSpec does not attach backend information to test files. All tests are defined independently of any backend. Therefore a Serverspec test file:
+
+```
+require 'serverspec'
+
+# Required by serverspec
+set :backend, :exec
+
+describe 'PHP' do
+  it 'has php' do
+    expect(command('php -v').exit_status).to eq(0)
+  end
+
+  it 'has the pear.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pear.php.net')
+  end
+
+  it 'has the pecl.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pecl.php.net')
+  end
+end
+```
+
+will become the following InSpec test file:
+
+```
+describe 'PHP' do
+  it 'has php' do
+    expect(command('php -v').exit_status).to eq(0)
+  end
+
+  it 'has the pear.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pear.php.net')
+  end
+
+  it 'has the pecl.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pecl.php.net')
+  end
+end
+```
+
+As you can see, the InSpec test files just focuses on tests and tries to avoid all clutter.
+
+## Nested describe blocks
+
+Serverspec and RSpec allow you to define nested describe blocks. We did a survey and found out that most users use nested describe blocks only to improve their output report. We believe the code structure should not change to improve the output of a report. Nevertheless we understand that nested describe blocks help you to structure test code. A sample code block looks like:
+
+```
+describe 'chef-server-directories' do
+  describe file('/etc/opscode') do
+    it { should be_directory }
+    it { should be_owned_by 'root' }
+  end
+
+  describe file('/etc/opscode-analytics') do
+    it { should be_directory }
+    it { should be_owned_by 'opscode' }
+    it { should be_grouped_into 'opscode' }
+  end
+
+  describe file('/var/log/opscode') do
+    it { should be_directory }
+    it { should be_owned_by 'opscode' }
+    it { should be_grouped_into 'opscode' }
+  end
+
+  describe file('/var/opt/opscode') do
+    it { should be_directory }
+    it { should be_owned_by 'root' }
+  end
+end
+```
+
+In InSpec you would split up groups into files.
+
+```
+tests
+├── server-directories.rb
+├── other-tests.rb
+└── further-tests.rb
+```
+
+Each file can have a top-level description of its content:
+
+```
+title "Chef Server Directories"
+
+describe file('/etc/opscode') do
+  it { should be_directory }
+  it { should be_owned_by 'root' }
+end
+
+describe file('/etc/opscode-analytics') do
+  it { should be_directory }
+  it { should be_owned_by 'opscode' }
+  it { should be_grouped_into 'opscode' }
+end
+
+describe file('/var/log/opscode') do
+  it { should be_directory }
+  it { should be_owned_by 'opscode' }
+  it { should be_grouped_into 'opscode' }
+end
+
+describe file('/var/opt/opscode') do
+  it { should be_directory }
+  it { should be_owned_by 'root' }
+end
+
+```
+
+## Are you supporting the `expect` syntax?
+
+Of course. We still prefer the `should` syntax for UX reasons. We did surveys with various types of customers like devops engineers, auditors, managers. All participants who prefered the `expect` syntax have been Ruby experts. All non-Ruby developers found it easier to understand the `should` syntax.
+
+### `should` syntax with InSpec
+
+```
+describe command('php -v') do
+  its('exit_status') { should eq 0 }
+end
+
+describe command('pear list-channels') do
+  its('stdout') { should include('pear.php.net')}
+end
+
+describe command('pear list-channels') do
+  its('stdout') { should include('pecl.php.net')}
+end
+```
+
+### `expect` syntax with InSpec
+
+```
+describe 'PHP' do
+  it 'has php' do
+    expect(command('php -v').exit_status).to eq(0)
+  end
+
+  it 'has the pear.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pear.php.net')
+  end
+
+  it 'has the pecl.php.net channel' do
+    expect(command('pear list-channels').stdout).to include('pecl.php.net')
+  end
+end
+```

data/docs/profiles.md

@@ -190,6 +190,7 @@ For example:
       - name: linux
         compliance: base/linux
 
+You need to `inspec vendor` the profile before uploading it to Chef Compliance version 1.7.7 or newer. The vendor subcommand fetches all dependent profiles and stores them in the `vendor` directory.
 
 ## Define in inspec.yml
 

data/lib/bundles/inspec-compliance/api.rb

@@ -143,5 +143,15 @@ Please login using `inspec compliance login https://compliance.test --user admin
       end
       headers
     end
+
+    def self.target_url(config, profile)
+      if config['server_type'] == 'automate'
+        target = "#{config['server']}/#{profile}/tar"
+      else
+        owner, id = profile.split('/')
+        target = "#{config['server']}/owners/#{owner}/compliance/#{id}/tar"
+      end
+      target
+    end
   end
 end

data/lib/bundles/inspec-compliance/cli.rb

@@ -116,6 +116,35 @@ module Compliance
       run_tests(tests, opts)
     end
 
+    desc 'download PROFILE', 'downloads a profile from Chef Compliance'
+    option :name, type: :string,
+      desc: 'Name of the archive filename (file type will be added)'
+    def download(profile_name)
+      o = options.dup
+      configure_logger(o)
+
+      config = Compliance::Configuration.new
+      return if !loggedin(config)
+
+      if Compliance::API.exist?(config, profile_name)
+        puts "Downloading `#{profile_name}`"
+
+        fetcher = Compliance::Fetcher.resolve(
+          {
+            compliance: profile_name,
+          },
+        )
+
+        # we provide a name, the fetcher adds the extension
+        _owner, id = profile_name.split('/')
+        file_name = fetcher.fetch(o.name || id)
+        puts "Profile stored to #{file_name}"
+      else
+        puts "Profile #{profile_name} is not available in Chef Compliance."
+        exit 1
+      end
+    end
+
     desc 'upload PATH', 'uploads a local profile to Chef Compliance'
     option :overwrite, type: :boolean, default: false,
       desc: 'Overwrite existing profile on Chef Compliance.'

data/lib/bundles/inspec-compliance/target.rb

@@ -53,23 +53,13 @@ EOF
         if !Compliance::API.exist?(config, profile)
           fail Inspec::FetcherFailure, "The compliance profile #{profile} was not found on the configured compliance server"
         end
-        profile_fetch_url = target_url(profile, config)
+        profile_fetch_url = Compliance::API.target_url(config, profile)
       end
       new(profile_fetch_url, config)
     rescue URI::Error => _e
       nil
     end
 
-    def self.target_url(profile, config)
-      if config['server_type'] == 'automate'
-        target = "#{config['server']}/#{profile}/tar"
-      else
-        owner, id = profile.split('/')
-        target = "#{config['server']}/owners/#{owner}/compliance/#{id}/tar"
-      end
-      target
-    end
-
     # We want to save compliance: in the lockfile rather than url: to
     # make sure we go back through the Compliance API handling.
     def resolved_source

data/lib/bundles/inspec-supermarket/api.rb

@@ -12,7 +12,7 @@ module Supermarket
     # displays a list of profiles
     def self.profiles(supermarket_url = SUPERMARKET_URL)
       url = "#{supermarket_url}/api/v1/tools-search"
-      _success, data = get(url, { type: 'compliance_profile', items: 100, order: 'recently_added' })
+      _success, data = get(url, { type: 'compliance_profile', items: 100 })
       if !data.nil?
         profiles = JSON.parse(data)
         profiles['items'].map { |x|

data/lib/bundles/inspec-supermarket/cli.rb

@@ -22,7 +22,7 @@ module Supermarket
 
       headline('Available profiles:')
       supermarket_profiles.each { |p|
-        li("#{p['tool_owner']}/#{p['slug']}")
+        li("#{p['tool_name']} #{mark_text(p['tool_owner'] + '/' + p['slug'])}")
       }
     end
 

data/lib/inspec/cli.rb

@@ -9,6 +9,7 @@ require 'thor'
 require 'json'
 require 'pp'
 require 'utils/json_log'
+require 'utils/latest_version'
 require 'inspec/base_cli'
 require 'inspec/plugins'
 require 'inspec/runner_mock'
@@ -223,6 +224,11 @@ class Inspec::InspecCLI < Inspec::BaseCLI # rubocop:disable Metrics/ClassLength
   desc 'version', 'prints the version of this tool'
   def version
     puts Inspec::VERSION
+    # display outdated version
+    latest = LatestInSpecVersion.new.latest
+    if Gem::Version.new(Inspec::VERSION) < Gem::Version.new(latest)
+      puts "\nYour version of InSpec is out of date! The latest version is #{latest}."
+    end
   end
 
   private

data/lib/inspec/version.rb

@@ -4,5 +4,5 @@
 # author: Christoph Hartmann
 
 module Inspec
-  VERSION = '1.8.0'.freeze
+  VERSION = '1.9.0'.freeze
 end

data/lib/resources/json.rb

@@ -49,7 +49,7 @@ module Inspec::Resources
         end
 
         # check if file is readable
-        if @file_content.empty? && @file.size > 0
+        if @file_content.nil? && @file.size > 0
           skip_resource "Can't read file \"#{@path}\""
           return @params = {}
         end

data/lib/resources/package.rb

@@ -143,11 +143,13 @@ module Inspec::Resources
       # parse data
       pkg = JSON.parse(cmd.stdout)[0]
       {
-        name: pkg.name.to_s,
+        name: pkg['name'],
         installed: true,
-        version: pkg.installed.version.to_s,
+        version: pkg['installed'][0]['version'],
         type: 'brew',
       }
+    rescue JSON::ParserError => _e
+      return nil
     end
   end
 

data/lib/resources/postgres_conf.rb

@@ -42,6 +42,20 @@ module Inspec::Resources
       res
     end
 
+    def method_missing(name)
+      param = params[name.to_s]
+      return nil if param.nil?
+      # extract first value if we have only one value in array
+      return param[0] if param.length == 1
+      param
+    end
+
+    def to_s
+      'PostgreSQL Configuration'
+    end
+
+    private
+
     def read_content
       @content = ''
       @params = {}
@@ -60,7 +74,10 @@ module Inspec::Resources
         raw_conf = read_file(to_read[0])
         @content += raw_conf
 
-        params = SimpleConfig.new(raw_conf).params
+        opts = {
+          assignment_re: /^\s*([^=]*?)\s*=\s*[']?\s*(.*?)\s*[']?\s*$/,
+        }
+        params = SimpleConfig.new(raw_conf, opts).params
         @params.merge!(params)
 
         to_read = to_read.drop(1)
@@ -87,9 +104,5 @@ module Inspec::Resources
     def read_file(path)
       @files_contents[path] ||= inspec.file(path).content
     end
-
-    def to_s
-      'PostgreSQL Configuration'
-    end
   end
 end

data/lib/resources/yum.rb

@@ -134,6 +134,10 @@ module Inspec::Resources
       return false if repo.nil?
       info['status'] == 'enabled'
     end
+
+    def to_s
+      "YumRepo #{shortname(info['id'])}"
+    end
   end
 
   # for compatability with serverspec

data/lib/utils/latest_version.rb

@@ -0,0 +1,20 @@
+# encoding: utf-8
+# author: Christoph Hartmann
+
+require 'json'
+require 'net/http'
+
+class LatestInSpecVersion
+  # fetches the latest version from rubygems server
+  def latest
+    uri = URI('https://rubygems.org/api/v1/gems/inspec.json')
+    res = Net::HTTP.start(uri.host, uri.port, use_ssl: uri.scheme == 'https') {|http|
+      http.read_timeout = 0.5
+      http.get(uri.path)
+    }
+    inspec_info = JSON.parse(res.body)
+    inspec_info['version']
+  rescue Exception # rubocop:disable Lint/RescueException
+    nil
+  end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: inspec
 version: !ruby/object:Gem::Version
-  version: 1.8.0
+  version: 1.9.0
 platform: ruby
 authors:
 - Dominik Richter
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-12-16 00:00:00.000000000 Z
+date: 2017-01-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: train
@@ -245,6 +245,7 @@ files:
 - docs/dsl_resource.md
 - docs/inspec_and_friends.md
 - docs/matchers.md
+- docs/migration.md
 - docs/plugin_kitchen_inspec.html.md
 - docs/profiles.md
 - docs/resources/apache_conf.md.erb
@@ -524,6 +525,7 @@ files:
 - lib/utils/find_files.rb
 - lib/utils/hash.rb
 - lib/utils/json_log.rb
+- lib/utils/latest_version.rb
 - lib/utils/modulator.rb
 - lib/utils/object_traversal.rb
 - lib/utils/parser.rb
@@ -549,7 +551,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.5.2
 signing_key: 
 specification_version: 4
 summary: Infrastructure and compliance testing.