Follow the instructions in the r10k or Code Manager drop-down menu to
add the module declaration to your Puppetfile. You also need to add its
dependencies. For example:
# Puppet comply module
mod 'puppetlabs/comply', '2.14.0'
# dependencies for comply
mod 'puppet/archive', '7.1.0'
mod 'puppetlabs/chocolatey', '8.0.0'
mod 'puppetlabs/inifile', '6.1.1'
mod 'puppetlabs/ruby_task_helper', '0.6.1'
mod 'puppetlabs/stdlib', '9.6.0'
mod 'puppetlabs/powershell', '6.0.0'
mod 'puppetlabs/registry', '5.0.1'
mod 'puppetlabs/pwshlib', '1.1.1'
If you don’t specify options, Code Manager installs
the latest version and does not update it automatically. To always have the
latest version installed, specify :latest and it updates
automatically when a new version is released. Make sure you are always
running the latest version of Security Compliance Management if you
intend to use the :latest keyword to update the Security Compliance Management module. To install a specific version
of the module that does not update automatically, specify the version number
as a string.
Important: If you choose a specific version of the module, it
must be the same as the Security Compliance Management
version. For example, version 2.3.0 of the module must be installed for Security Compliance Management 2.3.0.
Note: When configuring the Security Compliance Management
module for macOS, you must ensure Java is installed on
the Security Compliance Management nodes. Unlike Windows and Linux, there is no packaged JRE
for macOS within the module.