Configuring and using PE client tools

Use configuration files to customize how client tools communicate with the primary server.

For each client tool, you can create config files for individual machines (global) or for individual users. Configuration files are structured as JSON.

Save configuration files to these locations:

• Global:
  • *nix — /etc/puppetlabs/client-tools/
  • Windows — %ProgramData%\puppetlabs\client-tools
• User:
  • *nix — ~/.puppetlabs/client-tools/
  • Windows — %USERPROFILE%\.puppetlabs\client-tools

On managed client nodes where the operating system and architecture match the primary server, you can have PE manage Puppet code and orchestrator global configuration files using the puppet_enterprise::profile::controller class.

For example configuration files and details about using the various client tools, go to the documentation for each service:

Client tool	Documentation
Orchestrator	How Puppet orchestrator works Run Puppet on demand from the CLI Running tasks from the command line
Puppet access	Token-based authentication
Puppet code	Triggering Code Manager on the command line
PuppetDB	PuppetDB CLI

Related information

• Orchestrator configuration files
• Configure puppet-access
• Installing and configuring puppet-code