Analyze the impact of code changes
Impact analysis is a Continuous Delivery for Puppet Enterprise (PE) tool that shows you the potential impact that new Puppet code can have on your PE-managed infrastructure, without actually merging the new code. You can generate impact analysis reports on demand for commits in your control/module repos, and, if you add impact analysis to a repo's pipeline, Continuous Delivery for PE automatically generates a report on every proposed code change to that repo.
-
Configure impact analysis
Impact analysis is a Continuous Delivery for Puppet Enterprise (PE) tool that shows you the potential impact that new Puppet code can have on your PE-managed infrastructure, without actually merging the new code. When you add impact analysis to a control/module repo's pipeline, Continuous Delivery for PE automatically generates a report on every proposed code change to that repo. -
Generate impact analysis reports
Impact analysis reports show you the potential impact and risk of proposed code changes, so you can decide how, and if, you want to handle those potential changes. You can generate reports on demand or add impact analysis tasks to your pipelines to generate impact analysis reports for every change submitted to your repos. Impact analysis reports are generated by diffing the deployment's current catalog against a newly-generated catalog for your specified deployment conditions. -
Run impact analysis on fewer nodes
If an environment has a lot of nodes, it might take a long time for impact analysis to run. It is possible to only analyze a subset of your total nodes, but there are tradeoffs. -
Impact analysis limitations
Impact analysis has some technical limitations, and code changes can impact your infrastructure beyond what the impact analysis report displays.