Kubernetes Manifest Studio
Generate Deployment, Service, and Ingress YAML with a drift checklist.
OpenSee the destroys and replacements in a long plan before anyone types apply.
Drop plan text from CI or your local terminal.
See adds, changes, and destroys at a glance.
Databases and buckets raise the risk score.
Paste a human summary into your pull request.
A provider upgrade produces a 600-line plan, and buried in the middle is a database marked must be replaced. Reviewers skim plans like that. This summarizer pulls the counts and the dangerous lines to the top so they are hard to miss.
Paste the plain text output of terraform plan from your terminal or a CI log. The parser reads the # address will be comment lines and the +, ~, - and -/+ resource headers, then builds a table of every resource with its action and type. If a Plan: X to add line is present its numbers are used; otherwise counts come from the resource list. A checkbox hides everything except destroys and replacements.
Risk is scored from 0 to 100. Destroying or replacing a stateful resource (managed databases, buckets, volumes, secrets, key vaults, log groups, container registries and similar types across AWS, Google Cloud and Azure) adds the most, plain destroys and replacements add less, and plans with more than 40 resources get a small bump for review effort. It is a heuristic, so a low score does not clear a plan that removes an IAM role production depends on. The output is a markdown comment with a summary table, a warning callout and a collapsible resource list; you can preview the comment's Markdown before posting it.
Plan text is parsed in your browser and never uploaded. If the CI log might include credentials, run it through the secrets scanner first.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
No. The parser reads the human-readable plan text, so JSON produces no resources. Use the normal terraform plan output, or terraform show on a saved plan file without the -json flag.
Besides an explicit list of types, any type name containing fragments such as _db_, _database, _sql, _bucket, _volume, _disk, _secret, _vault or _backup is treated as stateful. That errs on the side of caution, so the occasional false alarm is expected.
When a Plan: line exists, its numbers are shown as Terraform reported them, and Terraform counts each replacement as both an add and a destroy. The separate replace column comes from the parsed resources.