TPI Import Dry Run#

Workflows → TDTPI Import Dry Runs

Reads a TPI, validates its content, and submits the resulting changes as a dry run transaction. No changes are committed. Use this to preview and verify changes before applying them. See TPIImport for a detailed walkthrough of the process.

Dependencies#

The TPIImportDryRun workflow has no dependencies.

Referenced resources#

The TPIImportDryRun workflow references a TPI via spec.tpi (required) -- the workbook to validate. The referenced TPI must live in the same namespace as the TPIImportDryRun workflow.

Examples#

YAMLkubectl

apiVersion: tpi.eda.nokia.com/v1
kind: TPIImportDryRun
metadata:
  name: example-import-dryrun
  namespace: eda
spec:
  tpi: example-tpi

cat << 'EOF' | kubectl apply -f -
apiVersion: tpi.eda.nokia.com/v1
kind: TPIImportDryRun
metadata:
  name: example-import-dryrun
  namespace: eda
spec:
  tpi: example-tpi

EOF

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.

SPEC

TPIImportDryRunSpec defines the desired state of TPIImportDryRun

#

STATUS

TPIImportDryRunStatus defines the observed state of TPIImportDryRun

#
#
Blocking validation or transaction errors that prevented the import from completing successfully. The workflow fails when this list is non-empty.
- #
#
Number of objects discovered
- #
#
#
Time consumed per stage
- #
#
#
#
Non-blocking parse issues. Populated when a sheet's action column is empty for every row: no object would have been imported from that sheet, so any issues found while parsing it are surfaced here instead of in .status.errors.
- #