Feature Request
Description:
Add an optional --manifest flag to the download, deploy, and delete commands. When provided, every detail of the operation — input parameters, resolved file URLs, checksums, per-file success/failure status, and error details — is recorded into a JSON-LD manifest file. When not provided, behavior is completely unchanged.
Feature importance:
There is currently no structured record of what was run, what succeeded, or what failed. A manifest gives every operation a reproducible, inspectable audit trail — the foundation for replay in a later milestone.
Alternative:
Plain text logging is unstructured and not replayable.
Key design points
- All three API functions gain exactly one new optional parameter
manifest_context=None — existing logic is completely untouched
- Schema versioned via
dbus:schemaVersion for forward compatibility
- Stores pre-construction CLI inputs (not computed outputs) so future replay can reconstruct operations correctly
- Per-file structured error capture (message, traceback) on failure
- Never writes user paths, API keys, tokens, or any sensitive data
Feature Request
Description:
Add an optional
--manifestflag to thedownload,deploy, anddeletecommands. When provided, every detail of the operation — input parameters, resolved file URLs, checksums, per-file success/failure status, and error details — is recorded into a JSON-LD manifest file. When not provided, behavior is completely unchanged.Feature importance:
There is currently no structured record of what was run, what succeeded, or what failed. A manifest gives every operation a reproducible, inspectable audit trail — the foundation for replay in a later milestone.
Alternative:
Plain text logging is unstructured and not replayable.
Key design points
manifest_context=None— existing logic is completely untoucheddbus:schemaVersionfor forward compatibility