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
- , , , , , , , , , ,
This module provides a custom bolt inventory plugin for Vagrant. This allows you to run Bolt from your Vagrant directory and the have the inventory automatically populated from Vagrant.
Configure the Bolt
inventory.yaml to use the plugin as follows:
version: 2 targets: - _plugin: task task: bolt_vagrant::targets
See the Bolt documentation for more info.
version: 2 targets: - _plugin: task task: bolt_vagrant::targets parameters: vagrant_dir: /Users/dylan/git/bolt_project_dir winrm_regex: win
vagrant_dir: The location of the Vagrant directory, defaults to
winrm_regex: A regular expression used to determine which machines should be connected to using winrm. Unfortunately Vagrant doesn't give that information out at the command line and there is no way of working it out. This regex is passed to
Regexp.new() as a string. Running the
targets.rb file manually will provide debugging info.
match: A regular expression used to determine which machines should be returned in the inventory. This regex is passed to
Regexp.new() as a string.
targets: Returns inventory from Vagrant for use in Bolt
Returns inventory from Vagrant for use in Bolt
Supports noop? false
Location of the directory containing the Vagrantfile. Defaults to the current directory.
Machines that match this will be connected to using winrm. Otherwise SSH will be used.
Machines that match this will be included in the inventory.
What are tasks?
Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.