Generating impact analysis reports
Impact analysis reports show you the potential impact and risk of proposed code changes. You can quickly review low-risk changes and enable additional scrutiny for high-risk changes. You can add an impact analysis task to each control/module repo pipeline 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. The results of this process are shown in the impact analysis report.
$environment
variable in your Puppet
manifest. Instead, use Hiera and class parameters.Add impact analysis to a control repo pipeline
If you add an impact analysis task to your control repo pipeline, an impact analysis report is automatically generated each time the pipeline runs and your specified conditions are met.
- Configure impact analysis.
- Construct a pipeline for your module that includes at least one deployment.
Each pipeline can have unlimited impact analysis tasks, but each stage in a pipeline can have only one impact analysis task. Additionally, an impact analysis task cannot be in the same stage as a deployment task.
This section explains how to add an impact analysis step to a pipeline constructed in the web UI. If you manage your pipelines with code, go to Structuring a .cd4pe.yaml file for guidance on adding impact analysis steps to your pipelines.
Add impact analysis to a module pipeline
If you add an impact analysis task to your module pipeline, an impact analysis report is automatically generated each time the pipeline runs and your specified conditions are met.
- Configure impact analysis.
- Construct a pipeline for your module that includes at least one deployment.
Each pipeline can have unlimited impact analysis tasks, but each stage in a pipeline can have only one impact analysis task. Additionally, an impact analysis task cannot be in the same stage as a deployment task.
This section explains how to add an impact analysis step to a pipeline constructed in the web UI. If you manage your pipelines with code, go to Structuring a .cd4pe.yaml file for guidance on adding impact analysis steps to your pipelines.
Generate an impact analysis report on demand
Without triggering a pipeline, you can generate an impact analysis report for any commit made to a control repo or module that Continuous Delivery for Puppet Enterprise (PE) monitors.