After enabling strict validation for agent run reports, some older modules produce invalid data structures in the final summary, crashing the puppetserver. The admin wants strict reporting for new modules but to exempt legacy modules temporarily. Which advanced approach balances new, strict enforcement with a phased legacy migration?
The “prod” environment references an old major version of a core module. A dev environment references the latest major version. Some modules in dev depend on that new version, but production needs stability. The business needs a phased approach. Which advanced environment strategy satisfies both dev module dependencies and production stability?
A newly published module has a tests/ directory with example usage files. You notice they lack any references to your environment or Hiera data. How should you leverage those .pp test files effectively?