Skip to content

Regenerate CLI reference (v0.43.1) - #590

Closed
Myothas wants to merge 1 commit into
masterfrom
cli-reference/v0.43.1
Closed

Myothas wants to merge 1 commit into
masterfrom
cli-reference/v0.43.1

Conversation

@Myothas

@Myothas Myothas commented Oct 19, 2026

Copy link
Copy Markdown
Member

Automated update generated by tools/gendocs in ankra-cli, with the CLI group in docs.json resynced by scripts/sync_cli_nav.py. Review the diff and merge to publish.

@ankra-platform

ankra-platform Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

✅ Run #240 succeeded

Run #240 for commit 697df0a (pull request #590).

Stage Step Outcome Duration
build build success 22s
checkout checkout success 16s
gate gate success 0s
publish publish skipped -
scan scan (tool=checkov) success 40s
scan scan (tool=semgrep) success 29s
scan scan (tool=trivy) success 46s

Open this run in Ankra

🔗 Details ↗ · Updated Oct 19, 2026, 12:30 PM UTC


Ankra AI review

Verdict: comments.

Docs-only regeneration of the CLI reference for v0.43.1; the version bump matches the PR title and the new sections (provenance, access-policy proposals, secret variables, stdin-based credential input) are internally consistent and describe sound security behaviour (unknown vs refused in provenance verify, audited secret reveals, deprecated on-command-line API keys). One clarity issue: the Proxmox-specific controller-count parenthetical was propagated into every provider's control-plane section.

Findings

  • [low] Proxmox-specific controller counts documented under every provider (reference/cli/cluster.mdx:817-818)
    This parenthetical ('1, 3 or 5 on Proxmox VE') now appears in the control-plane section for ankracloud, aws, digitalocean, hetzner, morpheus, ovh, scaleway and upcloud as well as proxmox. In the non-Proxmox sections it is irrelevant noise, and under ankracloud it is actively confusing since that provider has no Proxmox variant. Presumably the help text is shared across providers in the CLI generator; consider templating the count list per provider (as set-count already does for proxmox at line 6614) so each section only states the counts that provider accepts.

Reviewed commit 697df0a. This review is read-only and advisory.

Comment thread reference/cli/cluster.mdx
Comment on lines +817 to +818
Inspect and change the control plane configuration. The controller count
is 1 or 3 (1, 3 or 5 on Proxmox VE): etcd needs an odd number of voting

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.

[low] Proxmox-specific controller counts documented under every provider

This parenthetical ('1, 3 or 5 on Proxmox VE') now appears in the control-plane section for ankracloud, aws, digitalocean, hetzner, morpheus, ovh, scaleway and upcloud as well as proxmox. In the non-Proxmox sections it is irrelevant noise, and under ankracloud it is actively confusing since that provider has no Proxmox variant. Presumably the help text is shared across providers in the CLI generator; consider templating the count list per provider (as set-count already does for proxmox at line 6614) so each section only states the counts that provider accepts.

Ankra AI review. Read-only and advisory.

@Myothas

Myothas commented Oct 20, 2026

Copy link
Copy Markdown
Member Author

Superseded by the CLI reference regen for v0.44.0 (branch cli-reference/v0.44.0), which regenerates every page.

@Myothas Myothas closed this Oct 20, 2026
@Myothas
Myothas deleted the cli-reference/v0.43.1 branch October 20, 2026 21:12
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.

1 participant