Enable cached catalogs for use with the orchestrator (optional)
Enabling cached catalogs on your agents ensures does not enforce any catalog changes on your agents until you run an orchestrator job to enforce changes.
When you use the
orchestrator to enforce change in a environment (for
example, in the production
environment),
you want the agents in that environment to rely on their cached catalogs until you run an
orchestrator job that includes configuration changes for those agents. Agents in such
environments check in during the run interval (30 minutes by default) to reinforce
configuration in their cached catalogs, and apply new configuration only when you run with an orchestration job.
Note: This is an optional configuration. You can run Puppet on nodes with the
orchestrator in workflows that don't require cached catalogs.