From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sun, 7 Apr 2024 13:41:34 -0500
Subject: new repository

---
 devdocs/vagrant/provisioning%2Fpuppet_agent.html | 31 ++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 devdocs/vagrant/provisioning%2Fpuppet_agent.html

(limited to 'devdocs/vagrant/provisioning%2Fpuppet_agent.html')

diff --git a/devdocs/vagrant/provisioning%2Fpuppet_agent.html b/devdocs/vagrant/provisioning%2Fpuppet_agent.html
new file mode 100644
index 00000000..629d5e30
--- /dev/null
+++ b/devdocs/vagrant/provisioning%2Fpuppet_agent.html
@@ -0,0 +1,31 @@
+<h1 id="puppet-agent-provisioner">  Puppet Agent Provisioner </h1> <p><strong>Provisioner name: <code>puppet_server</code></strong></p> <p>The Vagrant Puppet agent provisioner allows you to provision the guest using <a href="https://www.puppetlabs.com/puppet">Puppet</a>, specifically by calling <code>puppet agent</code>, connecting to a Puppet master, and retrieving the set of modules and manifests from there.</p> <blockquote class="alert alert-warning"> <p><strong>Warning:</strong> If you are not familiar with Puppet and Vagrant already, I recommend starting with the <a href="shell">shell provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant is the best way to learn Puppet.</p> </blockquote>
+<h2 id="options">  Options </h2> <p>The <code>puppet_server</code> provisioner takes various options. None are strictly required. They are listed below:</p> <ul> <li>
+<p><a href="#binary_path"><code>binary_path</code></a> (string) - Path on the guest to Puppet's <code>bin/</code> directory.</p> </li> <li>
+<p><a href="#client_cert_path"><code>client_cert_path</code></a> (string) - Path to the client certificate for the node on your disk. This defaults to nothing, in which case a client cert will not be uploaded.</p> </li> <li>
+<p><a href="#client_private_key_path"><code>client_private_key_path</code></a> (string) - Path to the client private key for the node on your disk. This defaults to nothing, in which case a client private key will not be uploaded.</p> </li> <li>
+<p><a href="#facter"><code>facter</code></a> (hash) - Additional Facter facts to make available to the Puppet run.</p> </li> <li>
+<p><a href="#options-1"><code>options</code></a> (string or array) - Additional command line options to pass to <code>puppet agent</code> when Puppet is ran.</p> </li> <li>
+<p><a href="#puppet_node"><code>puppet_node</code></a> (string) - The name of the node. If this is not set, this will attempt to use a hostname if set via <code>config.vm.hostname</code>. Otherwise, the box name will be used.</p> </li> <li>
+<p><a href="#puppet_server"><code>puppet_server</code></a> (string) - Hostname of the Puppet server. By default "puppet" will be used.</p> </li> </ul> <h2 id="specifying-the-puppet-master">  Specifying the Puppet Master </h2> <p>The quickest way to get started with the Puppet agent provisioner is to just specify the location of the Puppet master:</p> <div class="highlight"><pre class="highlight ruby" data-language="ruby">Vagrant.configure("2") do |config|
+  config.vm.provision "puppet_server" do |puppet|
+    puppet.puppet_server = "puppet.example.com"
+  end
+end
+</pre></div>
+<p>By default, Vagrant will look for the host named "puppet" on the local domain of the guest machine.</p> <h2 id="configuring-the-node-name">  Configuring the Node Name </h2> <p>The node name that the agent registers as can be customized. Remember this is important because Puppet uses the node name as part of the process to compile the catalog the node will run.</p> <p>The node name defaults to the hostname of the guest machine, but can be customized using the Vagrantfile:</p> <div class="highlight"><pre class="highlight ruby" data-language="ruby">Vagrant.configure("2") do |config|
+  config.vm.provision "puppet_server" do |puppet|
+    puppet.puppet_node = "node.example.com"
+  end
+end
+</pre></div>
+<h2 id="additional-options">  Additional Options </h2> <p>Puppet supports a lot of command-line flags. Basically any setting can be overridden on the command line. To give you the most power and flexibility possible with Puppet, Vagrant allows you to specify custom command line flags to use:</p> <div class="highlight"><pre class="highlight ruby" data-language="ruby">Vagrant.configure("2") do |config|
+  config.vm.provision "puppet_server" do |puppet|
+    puppet.options = "--verbose --debug"
+  end
+end
+</pre></div><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
+    <a href="https://www.vagrantup.com/docs/provisioning/puppet_agent.html" class="_attribution-link">https://www.vagrantup.com/docs/provisioning/puppet_agent.html</a>
+  </p>
+</div>
-- 
cgit v1.2.3