Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

no_cached_catalogs

Adds a catalog terminus and indirector which allows user to stop the Puppet Agent caching catalogs on the local disk
Project URLRSS FeedReport issues

13,379 downloads

13,064 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.1 (latest)
  • 0.1.0
released Mar 28th 2016
This version is compatible with:
  • Puppet Enterprise >= 3.0.0
  • Puppet >= 3.0.0
  • , , , , , , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'dylanratcliffe-no_cached_catalogs', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add dylanratcliffe-no_cached_catalogs
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install dylanratcliffe-no_cached_catalogs --version 0.1.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

dylanratcliffe/no_cached_catalogs — version 0.1.1 Mar 28th 2016

no_cached_catalogs

Description

This module allows you to completely disable catalog caching on disk with the Puppet Agent. By default Puppet will cache the most recent catalog in the client_datadir, in order to disable this, install this module then add the following line to your puppet.conf:

catalog_cache_terminus = none

Or manage the setting in Puppet Code (recommended) using the inifile module

NOTE: As App Orchestration relies on agents being able to run against cached catalogs, using setting the catalog_cache_terminus to none will break App Orchestration.