Forge Home


This module installs the Hashicorp tools

Igor Bezerra de Oliveira



247 latest version

5.0 quality score

Version information

  • 1.0.2 (latest)
  • 1.0.1
  • 1.0.0
released Jul 21st 2021
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • CentOS

Start using this module


igorolivei/hashicorp_install — version 1.0.2 Jul 21st 2021


Welcome to the hashicorp_install. This module can install the Hashicorp tools binaries.

Table of Contents

  1. Description
  2. Setup - The basics of getting started with hashicorp_install
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


This module can install the tools developed by Hashicorp, hosted on

The tools you can install using it are consul, nomad, packer, terraform, vagrant and vault. Read more to learn how to use it.


What hashicorp_install affects

  • This module will install the unzip package.
  • It will also create a dummy file having the name on the pattern /usr/bin/<package_name>_<version>_installed to keep it idempotent.

Beginning with hashicorp_install

The very basic steps needed for a user to get the module up and running. This can include setup steps, if necessary, or it can be an example of the most basic use of the module.


  • Quick run (not recommended): puppet apply -e "include hashicorp_install"

  • Installing the packages you want (see more on Reference):

class { 'hashicorp_install':
  packages => {
    'consul'    => '1.8.2',
    'terraform' => '0.13.0',
    # ...


  • This module does not validate which packages are available for an specific OS architecture.
  • This module does not uninstall any installed binary.
  • This module does not configure anything, it only installs the binaries.



  • Create a topic branch from where you want to base your work. This is usually the master branch.
  • Push your changes to a topic branch in your fork of the repository.
  • Add yourself as a contributor in the Contributors sections of this file.
  • Update the module version on metadata.json.
  • Make sure your commits messages are well-written and describe clearly what has been changed.
  • Make sure you have tested your changes and nothing breaks.
  • Validate your module using pdk validate.
  • Submit a pull request to this repository.

Release Notes/Contributors/Etc.