Skip to content

docs: document dry-run, output contracts and import-url reference - #509

Open
Caesarsage wants to merge 4 commits into
microcks:masterfrom
Caesarsage:docs/cli-v1.0.3-updates
Open

Caesarsage wants to merge 4 commits into
microcks:masterfrom
Caesarsage:docs/cli-v1.0.3-updates

Conversation

@Caesarsage

Copy link
Copy Markdown
Contributor

Documentation-only pass closing the gaps between what 1.0.3 ships and what the
reference docs describe.

  • documentation/cmd/test.md — adds the dry-run surface, which existed only as a
    README section. All six flags with defaults, plus behaviour previously visible only in
    source: flags rejected without --dry-run (exit 2), the *-native image requirement,
    Podman auto-detection, localhost endpoint rewriting, and teardown on every exit path.
  • documentation/json-output.md (new) — one reference for consuming the CLI
    programmatically: stream discipline, format matrix, payload shapes, and the dry-run
    NDJSON event schema, which was documented nowhere despite being the contract editor
    and CI integrations bind to.
  • documentation/cmd/importURL.md — documents the
    <specURL>[:<mainArtifact>[:<secretName>]] grammar and the right-to-left parsing that
    keeps URLs-with-ports working (fix (cmd) : URL Port Corrupts Input in Import-URL Command #465).
  • README.md — adds --driver and a Reference table, and fixes a link to
    importUrl.md that 404s on GitHub (the file is importURL.md; it only resolved
    locally on case-insensitive filesystems).

Signed-off-by: caesarsage <destinyerhabor6@gmail.com>
Signed-off-by: caesarsage <destinyerhabor6@gmail.com>
Signed-off-by: caesarsage <destinyerhabor6@gmail.com>
Signed-off-by: caesarsage <destinyerhabor6@gmail.com>
@Caesarsage

Copy link
Copy Markdown
Contributor Author

cc: @Harsh4902 @Vaishnav88sk

for review

@Vaishnav88sk Vaishnav88sk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are non blocking. Just for format. 😉

Comment on lines +42 to +43
`test` is the only command that renders a full `TestResult`, so it is the only one
offering `yaml` and `github-actions`. Everything else exposes `text` or `json`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a minor contradiction here. The text states that test is the only command that renders a full TestResult, but the table in the very next section correctly points out that test get also renders a complete TestResult object when using --output json.
Suggestion: Reword this to clarify

Comment thread README.md
Comment on lines 73 to +74
| `import-dir` | Scan a directory and import API spec files. | [`import-dir`](documentation/cmd/importDir.md) |
| `import-url` | Import API spec files directly from a remote URL | [`import-url`](documentation/cmd/importUrl.md) |
| `import-url` | Import API spec files directly from a remote URL | [`import-url`](documentation/cmd/importURL.md) |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional: Could you also fix the alignment of the import-dir row right above it? It currently has an extra space after the command name.

@Vaishnav88sk

Copy link
Copy Markdown
Contributor

@Harsh4902 Above chnages are non-blocking. Docs are good. It is good to merge. 👍🏻

This branch was successfully deployed

1 active deployment
Build 52cde7aa Deployed Aug 26, 2026 by Caesarsage via build-verify-package #679
Sign up for free to 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