Validate

Check the target before you try to import the upgraded flow.

validate answers the next practical question after rewrite: will this artifact fit the target NiFi runtime? It can validate against an offline extensions manifest or a live NiFi API.

Back to site Supporting source

Offline validation

Use an extensions manifest when you want a fast preflight without calling a live NiFi. This is useful in CI or when platform teams want a stable target inventory file.

Live validation

Use a target NiFi API URL when you want the tool to check the running version, runtime extensions, and destination process-group readiness before an update. 

nifi-flow-upgrade validate \
  --input ./out/rewritten-flow.json.gz \
  --input-format flow-json-gz \
  --target-version 2.0.0 \
  --extensions-manifest ./manifests/nifi-2.0-core.yaml \
  --output-dir ./out

When validation fails

Treat it as a real signal. Missing runtime extensions, wrong target versions, or bad process-group readiness usually mean the import would fail or behave unexpectedly.