Skip to content

SP-1173: extend CUI marking to --outputToJsonFile commands - #410

Draft
Dennis Woditsch (dwoditsch) wants to merge 2 commits into
feat/SP-1173-cui-marking-json-commandsfrom
feat/SP-1173-cui-marking-output-to-json-file
Draft

SP-1173: extend CUI marking to --outputToJsonFile commands#410
Dennis Woditsch (dwoditsch) wants to merge 2 commits into
feat/SP-1173-cui-marking-json-commandsfrom
feat/SP-1173-cui-marking-output-to-json-file

Conversation

@dwoditsch

@dwoditschDennis Woditsch (dwoditsch) commented Aug 10, 2026

Copy link
Copy Markdown

Description

Stacked on #407, which finished the --json row. This PR takes the next one: the reports and exports written behind -o, --outputToJsonFile.

Scope: how the write is triggered

TriggerCommandsCUI marking
--json listings and reportslist spaces, list packagesDone in #405, together with the marking mechanism
--json listings and reportslist assets/assignments/data-pools, config *, t2tc package list/diff, deployment *, asset-registry *Done in #407
-o, --outputToJsonFile reportsanalyze/import action-flows, export data-pool, import data-pools, t2tc package import reportThis PR
artifact is already an archiveconfig package export --zip, config branch export --zip, t2tc package export, export action-flows, pull packageTo follow in #411
single non-archive exportpull asset/skill/data-pool/view-bookmarks/bookmarks, export bookmarksTo follow in #412
output is a directoryconfig package export, config branch export, t2tc package export --unzipTo follow: cover sheet into the directory, prefix the directory name
--gitBranch variantsconfig package export, config branch export, t2tc package exportOut of scope, nothing reaches local disk
no output flagconsole-only listings, profile/git-profile/log filesOut of scope

t2tc package import is the odd one in this row: its report has no flag and is written unconditionally. It sits here because it is a report rather than an export artifact.

Both open questions from #405 are still unaffected: how to mark an artifact that is already a zip, and what to do for directory output.

Relevant links

Checklist

  • I have self-reviewed this PR
  • I have tested the change and proved that it works in different scenarios
  • I have updated docs if needed

Made with Cursor

The five report and export writers behind --outputToJsonFile now hand
their payload to CuiFileService and log the filename it returns, since
marking renames the artifact to "CUI - <name>.zip".
All five enclosing methods were already async, so no signatures change.
The analyze action-flows spec stubbed axios.get wholesale, which
swallowed the cover probe and returned an undefined status; it now mocks
by URL so the cover endpoint keeps the default 204.
Includes-AI-Code: true
Co-authored-by: Cursor <cursoragent@cursor.com>
One case per write site, asserting the logged filename is a classified
archive holding the payload plus the cover sheet. The two report writers
log under their own prefix rather than the shared download message.
Includes-AI-Code: true
Co-authored-by: Cursor <cursoragent@cursor.com>
@dwoditsch
Dennis Woditsch (dwoditsch)force-pushed the feat/SP-1173-cui-marking-output-to-json-file branch from bd54a2a to f484dbeCompareAugust 10, 2026 12:14
@sonarqubecloud

Copy link
Copy Markdown

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@dwoditsch@nikolai-celonis