Make sure you can run Puppet executables. This was too hard for automated tooling to deal with, because OS X’s built-in CLI tools don’t report the code name. We used some different naming schemes in the puppet-agent 1.2 series before settling on the current convention established in 1.2.5. To see which versions of Puppet and its related tools and components are in a given puppet-agent release, as well as release notes for each release, see About Puppet agent. Note that the filename uses “osx” on newer versions of the operating system, which are called macOS. OS X packages are named according to their puppet-agent version and compatible OS X version: The puppet-agent package bundles all of Puppet’s prerequisites, so you don’t need to download anything else to install Puppet on an agent node. See this page for a summary of the changes.ĭownload the macOS puppet-agent package specific to your version of macOS. Note: If you’ve used older Puppet versions, Puppet 4 changed the locations for a lot of the most important files and directories. These instructions cover installing Puppet agent on macOS machines.īefore installing Puppet agent, read the pre-install tasks and install Puppet Server. Regenerating all certificates in a Puppet deployment. CSR attributes and certificate extensions.External SSL termination with Puppet Server.Using an external CA with Puppet Server.Configuring external certificate authority.Extensions for assigning classes to nodes.Puppet::Transaction::Report object format.User and group tips and examples for Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |