Impact analysis limitations
Impact analysis has some technical limitations, and code changes can impact your infrastructure beyond what the impact analysis report displays.
There are certain circumstances in which we can't reliably calculate the full impact of a code change. As an impact analysis user, it's critical that you understand these limitations exist, and you are aware of the possibility that code changes can have consequences for your infrastructure beyond what impact analysis shows.
Changes to an environment's
environment.conffile. Impact analysis can't determine the downstream impact of changes to an
- Brand-new code. Impact analysis can't determine the impact of new Puppet classes, facts, or functions that have never been applied to any of your nodes.
- Changes to functions. The impact of changes to a function cannot be analyzed.
- Changes to facts. The impact of changes to a fact cannot be analyzed.
- Changes to class names used in classification. Changes to class names that were previously classified in the classifier cannot be analyzed. A classification update in the classifier is required before Puppet can locate the newly renamed class.
- Imported resources. While impact analysis can provide information about nodes that export resources, impact analysis can't determine the impact to nodes that receive those exported resources.
- Sensitive data types. Any changes to data types marked as sensitive are not be analyzed.
- Alias metaparameter. Any resources using the alias metaparameter cannot be analyzed.
Changes to Embedded Puppet templates. The
impact of changes made to Embedded Puppet
.epp) or Embedded Ruby (
.erb) template files alone cannot be analyzed.
Patch fact generation script files. The
pe_patch_fact_generation.shfiles are excluded from impact analysis reports because these files always report a change of