If Puppet tasks are our imperative resources, Puppet plans are our Puppet manifests. Here, we combine multiple tasks and commands to form an orchestrated plan. These plans are written in the same DSL as Puppet code, although at the time of writing this book, only puppet functions can be used, and not many objects like resources or class are included.
In our sample plan, we're going to introduce two parameters:
- $enterprise: This is used to determine if pe-console-services should be checked in the plan (it is possible to use facts from the target or PuppetDB as well)
- $servers: This is a list of servers that's passed as a comma-separated list
Our task will clean up any existing stored logs and build a fresh set. This script will ...
