Repository navigation
feat: expose ovhcloud in the standalone CLI - #143
smini-digital wants to merge 1 commit into
Conversation
ovhcloud was wired into the library (installers, CLI_TOOLS, CLI_DOCS) but not into bin/cli.js, so the standalone CLI had no menu entry, no --ovhcloud flag and no full-setup step for it. Mirror the hcloud wiring: import, menu entry, switch case, --ovhcloud flag and help line, and a full-setup step (11 -> 12 steps). List ovhcloud in the README too.
There was a problem hiding this comment.
Code Review
This pull request integrates the OVHcloud CLI (ovhcloud) into the setup tool. The changes include updating the README.md documentation, importing and registering the configureOvhcloudCli installer in bin/cli.js, and adding support for it in the full setup flow, interactive menu, and command-line arguments. No issues were identified, and I have no feedback to provide.
|
🔏 Readiness attested — the Readiness summaryPR Readiness Check (#143, cb07d56) Tidy comments: SKIP (out of scope: tidy-comments covers Go |
|
Ratatoskr reviewed this pull request. Approved on Finished 2026-10-30 10:51 UTC. |
fank
left a comment
There was a problem hiding this comment.
APPROVE — 0 blocking findings.
Review details
Reviewed head cb07d56805a1b9a093da7473b73b2428bc973500 against main, including the existing installer and library integrations. The standalone wiring follows the repository's hcloud pattern and completes the missing entry point required by CLAUDE.md. No correctness or safety defect found.
Checks performed:
node --check bin/cli.js: passed.node --experimental-vm-modules --input-type=modulewith an inline harness loading the actual CLI source and synthetic dependency modules: passed assertions that--ovhcloudinvokes onlyconfigureOvhcloudCli, the menu entry follows hcloud and dispatches correctly, and full setup invokes OVHcloud once before LLM configuration with sequential[1/12]through[12/12]labels. This is isolated dispatch verification, not an installer or rendered UI test.npm test: unavailable (npm: command not found).node bin/cli.js --help: unavailable because checkout dependencies are absent (ERR_MODULE_NOT_FOUND: chalk). No packages installed or checkout files changed. Actual installation, authentication, and interactive rendering were not exercised.- GitHub reports lint, formatting, both CodeQL analyses, and the completed license check successful; another license check is skipped.
Optional test improvement: test/atl.test.js covers ATL helpers only; its six tests do not exercise this change and would also pass with the OVHcloud wiring reverted. Consider adding persistent CLI dispatch regression tests for the flag, menu, and full-setup paths.
Discussion follow-up: GraphQL review-thread enumeration returned no threads and no further pages. Resolved: 0; still open: 0; skipped: 0.
|
Ratatoskr status comment #issuecomment-6520869548: approved with 0 findings; nothing to change. |
Summary
ovhcloudwas added in #103 to the four library pieces (installer,lib/installers/index.js,lib/index.jsCLI_TOOLS,lib/llm/index.jsCLI_DOCS), so it shows up in environment-setup. The fifth piece thatCLAUDE.mdlists for every new tool —bin/cli.js— was not updated, so the standalone CLI had no menu entry, no--ovhcloudflag and no full-setup step for it.This mirrors the existing
hcloudwiring inbin/cli.js:configureOvhcloudCli[n/11]→[n/12]switchcase--ovhcloudflag, help line andelse ifbranchREADME: ovhcloud added to the tool list, the tool table and the docs list.
@fank — if leaving ovhcloud out of the standalone CLI was deliberate (environment-setup only), say so and I'll close this.
No ticket — authorized no-ticket fix.
Testing
npm test: 6/6 pass.npx eslint bin/cli.jsclean;npx prettier --check bin/cli.js README.mdclean.node bin/cli.js --helplists--ovhcloud Configure OVHcloud CLI only(exit 0; also confirms the new import resolves).configureOvhcloudCliitself (unchanged from feat: add OVHcloud CLI (ovhcloud) installer and docs #103) was not executed here.