Change impact analysis

Full workflow

Complete guide (limitations, CI, published lens): change-impact-analysis

Why use CCE

Before deprecating an API, rotating credentials, or merging a large refactor, teams need to know downstream code impact — who calls this SDK method or cloud operation. Impact analysis from architecture diagrams misses code-level callers.

CCE lists every call site for the changing API so release managers can scope testing, comms, and rollback plans.

Example command

cce -folder . -language AUTO -mapper-file https://releases.stackgen.com/cce/lenses/change-impact-analysis/latest/change-impact-analysis_lenses.yaml -filter all -format json -output change-impact-analysis.json

Published lens

https://releases.stackgen.com/cce/lenses/change-impact-analysis/latest/change-impact-analysis_lenses.yaml