Enable usage of custom puppet.conf
Update documentation with hiera_config_path
Detect Oracle Linux
Fix Dependency Issue with Puppet Version

When running the puppet-apply provisioner with a previous version of puppet than the
release package of the repository selected, there was a dependency issue where
puppet-common would need to be installed at that matching version _before_ installing
puppet at that version, yet puppet-common would be slated to install as the latest
version.

Only noticed issue on Debian/Ubuntu builds, did not test CentOS/RHEL flavors of Linux.
This is a critical issue for installing any version of puppet in test-kitchen that is a
lower version tag than the current release.

Also added an entry in gitignore to ignore any .gem files that are locally built during
gem development.

As well as added documentation for version numbers in the provisioner_options markdown
document.

Signed-off-by: "Jake Champlin" <jake.champlin@minted.com>
Allow Custom Puppet Apply Command to be configured

Allows custom puppet apply command to be written.
Need as a quick hack for having multiple puppet module directories and have dependencies
through each directory. Specifying the parent directory doesn't allow puppet to pull
init.pp manifests two directories down.

Allowing puppet_apply_command to be configured would allow a wide array of puppet apply
commands to be user defined in a string.

Signed-off-by: "Jake Champlin" <jake.champlin@minted.com>
Update Documentation for puppet_apply_command

Documentation Update

Signed-off-by: "Jake Champlin" <jake.champlin@minted.com>
Merge pull request #19 from chris-rock/patch-1

Detect Oracle Linux
Merge pull request #18 from ytsarev/doc_hiera

Update documentation with hiera_config_path
Merge pull request #17 from ytsarev/puppet_conf

Enable usage of custom puppet.conf
Merge pull request #20 from jake-minted/depend

Fix Dependency Issue with Puppet Version
Merge pull request #21 from jake-minted/apply

Apply
several enhancements plus 6 pull requests into the master code
add puppet environment option
add remove puppet repo option
Fixed metadata.json module name parsing

The module name inside the metadata.json is expected in the following
format: username-module instead username/module!

---
Source: https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#another-note-on-module-names

Another note on module names
Although the Puppet Forge expects to receive modules named username-
module, its web interface presents them as username/module. There isn’t
a good reason for this, and we are working on reconciling the two; in
the meantime, be sure to always use the username-module style in your
metadata files and when issuing commands.
---
Add Puppet Agent support
Add Puppet Agent support
Merge pull request #22 from grafjo/patch-1

Fixed metadata.json module name parsing
update gemspec title for puppet agent
recognise amazon linux