cargoship redact-receipt

Rewrites a run receipt so it can be attached to an issue

Synopsis

Reads the run receipt at RECEIPT and writes a copy with everything that identifies the fleet removed, for attaching to a bug report. Hosts are renumbered host-01, host-02 in the order the receipt lists them, consistently across every phase, so it still reads as a sequence of events on particular machines without naming them. Diff bodies are dropped entirely – an engine configuration diff carries join tokens and registry credentials – leaving the file paths and the reasons they changed, which is what a maintainer triages from. The cluster name, the operator, the management node and the command line go with them. What stays is the phase ledger, the package provenance, the outcome, and the architecture and OS of each host. Redaction is one way: the original is left untouched, because it is the audit record and this is only a copy to send.

cargoship redact-receipt [RECEIPT] [flags]

Examples

# Print a shareable copy of a run receipt
$ cargoship redact-receipt ./apply-20260928-143000.json

# Write one to a file, ready to attach to an issue
$ cargoship redact-receipt ./apply-20260928-143000.json -o ./share.json

Options

  -h, --help            help for redact-receipt
  -o, --output string   Write the redacted receipt to this path instead of standard output. The file is created readable only by its owner.

Options inherited from parent commands

      --log-file            Always write a full-verbosity debug log to a file, regardless of --log-level.
  -L, --log-format string   Select a logging format. Defaults to 'console'. Valid options are: 'console', 'json', 'dev'. (default "console")
  -l, --log-level string    Log level when running cargoship. Valid options are: warn, info, debug, trace (default "info")
      --no-color            Disable terminal color codes in logging and stdout prints.

SEE ALSO

• cargoship - CLI for cargoship installs