onceover 3.17.2 → 3.19.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2dca2d14bc7059827f3bcbe11eb8c0c00c43be5c37c45ac9fb3533562dab4e7b
-  data.tar.gz: d45c009adb4edae1b828fee5a0b51552c02bfc4dc7eefcb5b09a1832e8509170
+  metadata.gz: 645e450894eb3599a076f3c32c94ad73f88ad9177bb739e7ae56964bdeab1d22
+  data.tar.gz: 3ff596aa3b7a2be1edf18c9407a8fefe61b354e3dfb6a9fe4ef95f1a3e0c59d0
 SHA512:
-  metadata.gz: 13b3969909f9966f78663ba0568f96b557ef769c1a13a0d999d15d50a057ffa3584570b2c6e3c31b79aa09980c8088b62dc4ec665b073b60157243beb11d55cb
-  data.tar.gz: 3209f3771d3db26c9ba8f40a06225ac29b452fc012c08e9dfa6ea60cb485ad173448eb9d3aa491f0ed76d5ccdb068ffde61583a1a7fbe232fe352d5cd4874960
+  metadata.gz: 5ec23df5e72580ffa318b881def6a89f0fa336e11476dd9ce37ebdd3611976dfb26a0b48e3395f1e6d0c031fb63aaf517efcf9c7523c199115efafb2ecbae095
+  data.tar.gz: 3b505e9c89887b0656d197066d36b75004b2a899eed3941c93948c2349623412a6b78036af38e02eecac1a3f7131870be8027299337b807621363304f467f228

data/.gitattributes

@@ -0,0 +1,2 @@
+# force LF line endings, even when on Windows
+* text eol=lf

data/.github/workflows/tests.yaml

@@ -0,0 +1,40 @@
+name: Tests
+on:
+  - push
+  - pull_request
+jobs:
+  full_tests:
+    strategy:
+      fail-fast: false
+      matrix:
+        os:
+          - windows-2016
+          - ubuntu-latest
+          - macos-latest
+        puppet:
+          - "~> 5.0"
+          - "~> 6.0"
+          - "~> 7.0"
+        include:
+          - puppet: "~> 5.0"
+            ruby: 2.4
+          - puppet: "~> 6.0"
+            ruby: 2.5
+          - puppet: "~> 7.0"
+            ruby: 2.7
+
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+        env:
+          PUPPET_VERSION: ${{ matrix.puppet }}
+      - name: Set long paths on Windows
+        if: ${{ matrix.os == 'windows-2016' }}
+        run: Set-ItemProperty 'HKLM:\System\CurrentControlSet\Control\FileSystem' -Name 'LongPathsEnabled' -value 1
+      - env:
+          PUPPET_VERSION: ${{ matrix.puppet }}
+        run: bundle exec rake full_tests

data/.rubocop.yml

@@ -1,4 +1,6 @@
 AllCops:
+  TargetRubyVersion: 2.4 # this should match the oldest version in .github/workflows/tests.yaml's matrix 
+  NewCops: enable
   Include:
     - "lib/**/*.rb"
     - "ext/**/*.rb"
@@ -10,6 +12,21 @@ AllCops:
     - "tasks/**/*"
     - "vendor/**/*"
 
+# Turning off some failing checks until it is determined which one is breaking things
+Style/AccessorGrouping:
+  Enabled: false
+Style/CaseLikeIf:
+  Enabled: false
+Style/GlobalStdStream:
+  Enabled: false
+Style/RedundantRegexpCharacterClass:
+  Enabled: false
+Style/SoleNestedConditional:
+  Enabled: false
+Style/StringConcatenation:
+  Enabled: false
+# end turning things off for debugging
+
 Layout/ConditionPosition:
   Enabled: true
 
@@ -19,7 +36,7 @@ Lint/ElseLayout:
 Lint/UnreachableCode:
   Enabled: true
 
-Lint/UselessComparison:
+Lint/BinaryOperatorWithIdenticalOperands:
   Enabled: true
 
 # MAYBE useful - no return inside ensure block.
@@ -650,7 +667,8 @@ Style/ZeroLengthPredicate:
 
 Bundler/OrderedGems:
   Enabled: false
-  # Enforce LF line endings, even when on Windows
+
+# Enforce LF line endings, even when on Windows
 Layout/EndOfLine:
   EnforcedStyle: lf
 

data/Gemfile

@@ -17,16 +17,3 @@ end
 if File.exist?(File.join(Dir.home, '.gemfile'))
   eval(File.read(File.join(Dir.home, '.gemfile')), binding)
 end
-
-if ENV['APPVEYOR'] == 'True'
-  # R10k needs to be pinned to this until the next release after 3.1.1
-  # in order to not have symlinks and therefor work on windows
-  gem 'r10k', git: 'https://github.com/puppetlabs/r10k.git'
-end
-
-group :development do
-  gem 'cucumber', '~> 2.0'
-  gem 'pry', '~> 0.10.0'
-  gem 'rubocop', '~> 0.82.0'
-  gem 'rubygems-tasks', '~> 0.2.0'
-end

data/README.md

@@ -2,21 +2,23 @@
 
 *The gateway drug to automated infrastructure testing with Puppet*
 
-Onceover is a tool to automatically run basic tests on an entire Puppet controlrepo. It includes automatic parsing of the `Puppetfile`, `environment.conf` and others in order to stop silly mistakes ever reaching your Puppet Master!
+Onceover is a tool to automatically run basic tests on an entire Puppet control repository.
 
-**🍺🥳 New in v3.17.1: Heaps more Windows fixes! Windows code is now more likely to compile on Non-Windows.**
+It includes automatic parsing of the `Puppetfile`, `environment.conf` and others in order to stop silly mistakes ever reaching your Puppet Master!
+
+**New in v3.19.1: I've reversed the decision to have onceover use `site.pp` in the same way Puppet does. From now on your `manifest` setting in `environment.conf` will be ignored and your `site.pp` will only be used if you explicitly set the `manifest` option in the CLI or config file.**
+
+[![Build Status](https://travis-ci.com/dylanratcliffe/onceover.svg?branch=master)](https://travis-ci.com/dylanratcliffe/onceover) [![Build status](https://ci.appveyor.com/api/projects/status/2ys2ggkgln69hmyf/branch/master?svg=true)](https://ci.appveyor.com/project/dylanratcliffe/onceover/branch/master)
 
 ## Table of Contents
 
   - [Overview](#overview)
   - [Quick Start](#quick-start)
-  - [Installation](#installation)
-  - [Config files](#config-files)
+  - [Configuration](#configuration)
     - [onceover.yaml](#onceoveryaml)
-    - [factsets](#factsets)
-    - [Hiera Data](#hiera-data)
-    - [r10k](#r10k)
-      - [r10k Config](#r10k-config)
+    - [Factsets](#factsets)
+    - [Hiera](#hiera)
+    - [Puppetfile](#puppetfile)
   - [Spec testing](#spec-testing)
     - [Adding your own spec tests](#adding-your-own-spec-tests)
   - [Using Workarounds](#using-workarounds)
@@ -32,120 +34,220 @@ Onceover is a tool to automatically run basic tests on an entire Puppet controlr
     - [Rake tasks](#rake-tasks)
       - [generate_fixtures](#generate_fixtures)
 
+## Overview
+
+This gem provides a toolset for testing _Puppet control repository_ (ie. Repos used with r10k).
+
+The main purpose of this project is to provide a set of tools to help smooth out the process of setting up and running `rspec-puppet` tests for a controlrepo.
+
+Due to the fact that controlrepos are fairly standardised in nature it seemed ridiculous that you would need to set up the same testing framework that we would normally use within a module for a controlrepo. This is because at this level we are normally just running very basic tests that cover a lot of code. It would also mean that we would need to essentially duplicated our `Puppetfile` into a `.fixtures.yml` file, along with a few other things.
+
+This toolset requires some [configuration](#configuration) before it can be used so definitely read that section before getting started.
+
 ## Quick Start
 
-**Note:** This assumes you are inside the root of your controlrepo.
+**Note:** This assumes you are inside the root of your control-repo.
 
-Install the Gem:
+1. Add `onceover` to your `Gemfile`:
 
-`gem install onceover`
+    ```ruby
+    gem 'onceover'
+    ```
 
-Set up your config:
+1. Run _Bundler_ to install `onceover`
 
-`onceover init`
+    ```shell
+    bundle install
+    ```
 
-Run your spec tests!
+1. Set up your configuration
 
-`onceover run spec`
+    ```shell
+    bundle exec onceover init
+    ```
+1. Run your spec tests!
 
-**Hint:** Don't forget you can use Bundler to install onceover by adding this to your Gemfile:
+    ```shell
+    bundle exec onceover run spec
+    ```
 
-```ruby
-gem 'onceover'
-```
+## Configuration
 
-Here is an example using Bundler:
+This project uses one main config file to determine what Puppet classes we should be testing and how: [onceover.yaml](#onceoveryaml).
 
-Install the Gem:
+As `onceover` tests Puppet classes, it need sets of facts to compile the Puppet code against, these are stored in [factsets](#factsets).
 
-`bundle install`
+### onceover.yaml
 
-Set up your config:
+Usually located at `spec/onceover.yaml`, this path could be overrided with environment variable: `ONCEOVER_YAML`.
 
-`bundle exec onceover init`
+Hopefully this config file will be fairly self explanatory once you see it, but basically this is the place where we define what classes we want to test and the [factsets](#factsets) that we want to test them against.
 
-Run your spec tests!
+#### Main settings
 
-`bundle exec onceover run spec`
+- `classes`
 
-## Overview
+    A list (array) of classes that we want to test
 
-This gem provides a toolset for testing Puppet Controlrepos (Repos used with r10k). The main purpose of this project is to provide a set of tools to help smooth out the process of setting up and running `rspec-puppet` tests for a controlrepo. Due to the fact that controlrepos are fairly standardised in nature it seemed ridiculous that you would need to set up the same testing framework that we would normally use within a module for a controlrepo. This is because at this level we are normally just running very basic tests that cover a lot of code. It would also mean that we would need to essentially duplicated our `Puppetfile` into a `.fixtures.yml` file, along with a few other things.
+    Classes are specified as string or **regular expressions**.
+    The recommended setting to have a good coverage is `/^role::/` if you use [roles and profiles method](https://puppet.com/docs/pe/latest/the_roles_and_profiles_method.html) and if you dont, you [should](https://puppet.com/docs/pe/2019.8/the_roles_and_profiles_method.html).
 
-This toolset requires some config before it can be used so definitely read that section before getting started.
+- `nodes`
 
-## Installation
+    A list (array) of nodes that we want to test against.
 
-`gem install onceover`
+    The nodes that we list here map directly to a [factset](#factsets), e.g. `Debian-7.8-64`
 
-This gem can just be installed using `gem install` however I would recommend using [Bundler](http://bundler.io/) to manage your gems.
+- `node_groups`
 
-## Config Files
+    An hash of named node groups.
 
-This project uses one main config file to determine what classes we should be testing and how, this is [onceover.yaml](#onceoveryaml). The `onceover.yaml` config file provides information about what classes to test when, however it needs more information than that:
+    We can create groups by simply specifying an array of nodes to be in the group, or use the subtractive [include/exclude syntax](#includeexclude-syntax).
 
-If we are doing spec testing we need sets of facts to compile the puppet code against, these are stored in [factsets](#factsets). (A few are provided out of the box for you)
+    **Note:** A _node group_ named `all_nodes` is automatically created by `onceover`.
 
-### onceover.yaml
+    **Important:** The names used for the actual `class_groups` and `node_groups` must be unique.
 
-`spec/onceover.yaml` _(override with environment variable: `ONCEOVER_YAML`)_
+- `class_groups`
 
-Hopefully this config file will be fairly self explanatory once you see it, but basically this is the place where we define what classes we want to test and the [factsets](#factsets) that we want to test them against. The config file must contain the following sections:
+    An hash of named class groups.
 
-**classes:** A list (array) of classes that we want to test, usually this would be your roles, possibly profiles if you want. (If you don't know what roles and profiles are please [READ THIS](http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/)). To make life easier you can also specify one or many **regular expressions** in this section. A good one to start with would be `/^role::/`. Regular expressions are just strings that start and end with a forward slash.
+    We can create groups by simply specifying an array of classes (string or regexp) to be in the group, or use the subtractive [include/exclude syntax](#includeexclude-syntax).
 
-**nodes:** The nodes that we want to test against. The nodes that we list here map directly to a [factset](#factsets).
+    **Note:** A _class group_ named `all_classes` is automatically created by `onceover`.
 
-**node_groups:** The `node_groups` section is just for saving us some typing. Here we can set up groups of nodes which we can then refer to in our test matrix. We can create groups by simply specifying an array of servers to be in the group, or we can use the subtractive *include/exclude* syntax. The names used for the actual `class_groups` and `node_groups` must be unique.
+    **Important:** The names used for the actual `class_groups` and `node_groups` must be unique.
 
-**class_groups:** The `class_groups` section is much the same as the `node_groups` sections, except that it creates groups of classes, not groups of nodes (duh). All the same rules apply and you can also use the *include/exclude* syntax. This, like the classes section can also accept regular expressions. This means that as long as you name your roles according to a naming convention that includes the desired operating system, you should be able to define your class groups once and never touch them again. The names used for the actual `class_groups` and `node_groups` must be unique.
+- `test_matrix`
 
-**test_matrix:** This where the action happens! This is the section where we set up which classes are going to be tested against which nodes. It should be an array of hashes with the following format:
+    An array of hashes with the following format:
 
-```yaml
-  - {nodes_to_test}: # The name of a node or node group
-      classes: '{classes_to_test}' # the name of a class or
-      tests: '{all_tests|acceptance|spec}' # acceptance deprecated/broken, set to spec
-      {valid_option}: {value} # Check the doco for available options
-```
+    ```yaml
+      - {nodes_to_test}: # The name of a node or node group
+          classes: '{classes_to_test}' # the name of a class or
+          tests: '{all_tests|acceptance|spec}' # acceptance deprecated/broken, set to spec
+          {valid_option}: {value} # See below
+    ```
 
-Why an array of hashes? Well, that is so that we can refer to the same node or node group twice, which we may want/need to do.
+    Valid options:
 
-In the example below we have referred to `centos6a` and `centos7b` in all of our tests as they are in `all_nodes`, `non_windows_servers` and `centos_severs`. However we have *left the more specific references to last*. This is because entries in the test_matrix will override entries above them if applicable. Meaning that we are still only testing each class on the two Centos servers once (Because the gem does de-duplication before running the tests), but also making sure we run `roles::frontend_webserver` twice before checking for idempotency.
+    - `tags`
 
-**functions** In this section we can add functions that we want to mock when running spec tests. Each function takes the following arguments:
+        Default: `nil`
 
-- **returns** *Optional: A value to return*
+       One or many tags that tests in this group should be tagged with.
+       This allows you to run only certain tests using the `--tags` command line parameter.
 
-**before and after conditions** We can set `before` and `after` blocks before each spec test. These are usually used when the functions to stub are conditional: stub function `x` if the OS is windows, stub function `y` if the fact java_installed is true. The facts are available through the `node_facts` hash and the trusted facts as `trusted_facts`.
+#### Advanced settings
 
-```yaml
-before:
-  - "Puppet::Util::Platform.stubs(:'windows?').returns(node_facts['kernel'] == 'windows')"
+- `functions`
 
-after:
-  - "puts 'Test finished running'"
-```
+    Default: `nil`
+
+    In this section we can add functions that we want to mock when running spec tests.
+
+    Each function takes the `return` arguments, e.g.
+
+    ```yaml
+    functions:
+      puppetdb_query:
+        returns: []
+    ```
+
+- `before`
+
+    Default: `nil`
+
+    A block to run **before** each spec test.
+
+    For example, this can be used when the functions to stub are conditional, the following stub function `x` if the OS is windows, stub function `y` if the fact `java_installed` is true.
+
+    **Note**: The facts are available through the `node_facts` hash and the trusted facts as `trusted_facts`.
+
+    Example:
+    ```yaml
+    before:
+      - "Puppet::Util::Platform.stubs(:'windows?').returns(node_facts['kernel'] == 'windows')"
+    ```
+
+- `after`
+
+    Default: `nil`
+
+    A block to run **after** each spec test.
+
+    **Note**: The facts are available through the `node_facts` hash and the trusted facts as `trusted_facts`.
+
+    Exmaple:
+    ```yaml
+    after:
+      - "puts 'Test finished running'"
+    ```
+
+- `include_spec_files`
+
+    Default: `[**/*]`
+
+    Glob to select additionnal files to be run during `onceover` spec tests.
+
+    Default is to select all files located in the repo spec directory, usually `spec/`.
+    If you have some RSpec tests that depend on a different RSpec configuration than `onceover` or want, for example, to have a different job in your CI to run your own unit tests, you can use this option to select which spec files to run during `onceover` spec tests.
+
+- `opts`
+
+    Default: `{}`
+
+    This setting overrides defaults for the `Onceover::Controlrepo` class' `opts` hash.
+
+    Example:
+    ```yaml
+    opts:
+      :facts_dirs:                           # Remember: `opts` keys are symbols!
+        - 'spec/factsets'                    # Limit factsets to files in this repository
+      :debug: true                           # Set the `logger.level` to debug
+      :profile_regex: '^(profile|site)::'    # Profiles include a legacy module named `site::`
+      :facts_files:                          # Factset filenames use the extension`.facts` instead of `.json`
+        - 'spec/factsets/*.facts'
+      :manifest: 'manifests/site.pp'         # Manifest to use while compiling (nil by default)
+    ```
+
+#### Include/Exclude syntax
 
-**opts** The `opts` section overrides defaults for the `Onceover::Controlrepo` class' `opts` hash.
+This can be used with either `node_groups` or `class_groups` and allows us to save some time by using existing groups to create new ones e.g.
 
 ```yaml
-opts:
-  :facts_dirs:        # Remember: `opts` keys are symbols!
-    - 'spec/factsets' # Limit factsets to files in this repository
-  :debug: true        # set the `logger.level` to debug
+node_groups:
+  windows_nodes: # This has to be defined first
+    - sevrer2008r2
+    - server2012r2
+  non_windows:
+    include: 'all_nodes' # Start with all nodes
+    exclude: 'windows_nodes' # Then remove the windows ones from that list
 ```
 
+It's important to note that in order to reference a group using the *include/exclude* syntax is has to have been defined already i.e. it has to come above the group that references it
+
+#### Examples
+
+##### Minimal
+
 ```yaml
-opts:
-  # profiles include a legacy module named `site::`
-  :profile_regex: '^(profile|site)::'
+classes:
+  - /^role::/
 
-  # factset filenames use the extension`.facts` instead of `.json`
-  :facts_files:
-    - 'spec/factsets/*.facts'
+nodes:
+  - Debian-10-amd64
+
+test_matrix:
+  - all_nodes:
+      classes: 'all_classes'
+      tests: 'spec'
 ```
 
+##### Advanced
+
+In the example below we have referred to `centos6a` and `centos7b` in all of our tests as they are in `all_nodes`, `non_windows_servers` and `centos_severs`. However we have *left the more specific references to last*. This is because entries in the test_matrix will override entries above them if applicable. Meaning that we are still only testing each class on the two Centos servers once (Because the gem does de-duplication before running the tests), but also making sure we run `roles::frontend_webserver` twice before checking for idempotency.
+
 A full example:
 
 ```yaml
@@ -155,7 +257,7 @@ classes:
   - 'roles::load_balancer'
   - 'roles::syd_f5_load_balancer'
   - 'roles::windows_server'
-  - '/^role/'
+  - '/^role/'                     # Note that this regex format requires `/`
 
 nodes:
   - centos6a
@@ -209,47 +311,26 @@ functions:
 opts:
   :facts_dirs:
     - spec/factsets
+  :profile_regex: '^(profile|site)::'   # Note that this regex _doesn't_ use `/`
 ```
 
-**Include/Exclude syntax:** This can be used with either `node_groups` or `class_groups` and allows us to save some time by using existing groups to create new ones e.g.
-
-```yaml
-node_groups:
-  windows_nodes: # This has to be defined first
-    - sevrer2008r2
-    - server2012r2
-  non_windows:
-    include: 'all_nodes' # Start with all nodes
-    exclude: 'windows_nodes' # Then remove the windows ones from that list
-```
+### Factsets
 
-It's important to note that in order to reference a group using the *include/exclude* syntax is has to have been defined already i.e. it has to come above the group that references it (Makes sense right?)
+Factsets are used by the onceover gem to generate spec tests, which compile a given class against a certain set of facts.
 
-#### Optional test parameters
+This gem comes with a few pre-canned factsets, these are listed under the `nodes` sections of `onceover.yaml` when you run `onceover init`.
 
-**tags** *Default: nil*
+You can, and its a good pratice, add your own factsets by putting them in `spec/factsets/*.json`.
 
-One or many tags that tests in this group should be tagged with. This allows you to run only certain tests using the `--tags` command line parameter. **NOTE:** Custom spec tests will always be run as they are not subject to tags
+To generate these factsets all we need to do is log onto a real machine that has puppet installed and run:
 
-### factsets
-
-This gem comes with a few pre-canned factsets. These are listed under the `nodes` sections of `onceover.yaml` when you run `onceover init`. You can also add your own factsets by putting them in:
-
-`spec/factsets/*.json`
-
-Factsets are used by the onceover gem to generate spec tests, which compile a given class against a certain set of facts. To create these factsets all we need to do is log onto a real machine that has puppet installed and run:
-
-`puppet facts`
-
-Which will give raw json output of every fact which puppet knows about. Usually I would recommend running this on each of the types of machines that you run in your infrastructure so that you have good coverage. To make life easier you might want to direct it into a file instead of copying it from the command line:
-
-`puppet facts > fact_set_name.json`
-
-Once we have our factset all we need to do is copy it into `spec/factsets/` inside our controlrepo and commit it to version control. Factsets are named based on their filename, not the name of the server they came from (Although you can, if you want). i.e the following factset file:
+```shell
+puppet facts > fact_set_name.json
+```
 
-`spec/factsets/server2008r2.json`
+Its recommended to run this on each of the types of nodes that you run in your infrastructure to have good coverage.
 
-Would map to a node named `server2008r2` in `onceover.yaml`
+Factsets are named based on their filename, i.e. `myfactset` in `onceover.yaml` refers `spec/factsets/myfactset.json`
 
 #### Trusted Facts
 
@@ -270,13 +351,17 @@ You can add trusted facts to the factsets by creating a new section called trust
 
 Notice that the `extensions` part is implied. The first fact in that example translates to `$trusted['extensions']['pp_role']` in Puppet code.
 
-### Hiera Data
+### Hiera
 
-If you have hiera data inside your controlrepo (or somewhere else) Onceover can be configured to use it. It is however worth noting the the `hiera.yaml` file that you currently use may not be applicable for testing right away. For example; if you are using `hiera-eyaml` I recommend creating a `hiera.yaml` purely for testing that simply uses the `yaml` backend, meaning that you don't need to provide the private keys to the testing machines.
+If you have hiera data inside your controlrepo (or somewhere else) `onceover` can be configured to use it.
+It is however worth noting the `hiera.yaml` file that you currently use may not be applicable for testing right away.
+For example; if you are using `hiera-eyaml` I recommend creating a `hiera.yaml` purely for testing that simply uses the `yaml` backend, meaning that you don't need to provide the private keys to the testing machines.
 
-It is also worth noting that any hiera hierarchies that are based on custom facts will not work unless those facts are part of your factsets. Trusted facts will also not work at all as the catalogs are being compiled without the node's certificate. In these instances it may be worth creating a hierarchy level that simply includes dummy data for testing purposes in order to avoid hiera lookup errors.
+It is also worth noting that any hiera hierarchies that are based on custom facts will not work unless those facts are part of your factsets.
+Trusted facts will also not work at all as the catalogs are being compiled without the node's certificate.
+In these instances it may be worth creating a hierarchy level that simply includes dummy data for testing purposes in order to avoid hiera lookup errors.
 
-### r10k
+### Puppetfile
 
 Organisations often reference modules from their own git servers in the `Puppetfile`, like this:
 
@@ -286,7 +371,9 @@ mod "puppetlabs-apache",
   :tag => "v5.4.0"
 ```
 
-Under the hood, Onceover uses r10k to download the modules in your `Puppetfile`. If you get errors downloading modules from Git, its because `r10k`'s call to your underlying `git` command has failed. Onceover tells you the command that `r10k` tried to run, so if you get an error like this:
+Under the hood, `onceover` uses `r10k` to download the modules in your `Puppetfile`.
+If you get errors downloading modules from `git`, its because `r10k`'s call to your underlying `git` command has failed.
+`onceover` tells you the command that `r10k` tried to run, so if you get an error like this:
 
 ```
 INFO     -> Updating module /Users/dylan/control-repo/.onceover/etc/puppetlabs/code/environments
@@ -321,7 +408,7 @@ Warning: Permanently added 'git.megacorp.com,123.456.789.101' (RSA) to the list
 
 The other way to resolve this would have been to install the `ssh_askpass` program, but this can spam the screen with modal dialogs on some platforms.
 
-#### r10k Config
+#### r10k configuration
 
 If you have custom r10k config that you want to use, place the `r10k.yaml` file in one of the following locations:
 
@@ -701,3 +788,7 @@ Cheers to all of those who helped out:
   - @tequeter
   - @alexjfisher
   - @smortex
+  - @16c7x
+  - @neomilium
+  - @chlawren
+