didericis
cd9f023f3d
prd-number-check / require-numbered-prds (pull_request) Successful in 11s
tracker-policy-pr / check-pr (pull_request) Successful in 14s
test / unit (pull_request) Successful in 59s
test / integration-docker (pull_request) Successful in 1m6s
test / coverage (push) Successful in 21s
test / image-input-builds (push) Successful in 44s
test / image-input-builds (pull_request) Successful in 1m15s
test / unit (push) Successful in 57s
test / coverage (pull_request) Successful in 20s
lint / lint (push) Successful in 1m3s
Update Quality Badges / update-badges (push) Successful in 1m12s
test / integration-docker (push) Successful in 1m0s
`doctor` told users to run `./cli.py backend setup`. cli.py is a four-line wrapper at the repo root that calls bot_bottle.cli:main, and it does not ship — [tool.setuptools.packages.find] includes only bot_bottle*, so anyone who installed rather than cloned has no such file. Confirmed against a real install: the user's tree contains exactly one executable, `bot-bottle`, and no cli.py anywhere, while doctor recommended `./cli.py` three times. Invisible in development, where ./cli.py works fine from a checkout, which is why only a clean-install test surfaced it. The two entry points are the same code, so the fix is to name the one that always exists. 141 replacements across 45 files: the runtime messages that caused this, plus README, docs, PRDs, research notes and test prose, so nothing teaches the invocation a user cannot run. scripts/demo.sh is deliberately untouched — it *executes* ./cli.py from a checkout, where that is the correct and available path. Verified end to end: a sandbox install now reports "Run: bot-bottle backend setup --backend=firecracker", and bot-bottle is on that user's PATH. Unit suite unchanged against the pre-existing baseline. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WEfZZhakx13bxTfXcZCoS5
47 lines
1.5 KiB
Python
47 lines
1.5 KiB
Python
"""`backend` CLI command — generic host setup/status across backends.
|
|
|
|
`bot-bottle backend setup [--backend=NAME]` provisions (or points at how
|
|
to provision) the chosen backend's one-time host prerequisites.
|
|
`bot-bottle backend status [--backend=NAME]` reports readiness.
|
|
`bot-bottle backend teardown [--backend=NAME]` undoes setup (uninstall).
|
|
|
|
All dispatch to the backend's `setup()` / `status()` / `teardown()`
|
|
classmethods, so there are no backend-specific commands — swapping
|
|
backends is just a different `--backend` (or `$BOT_BOTTLE_BACKEND`, or
|
|
the host default).
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import argparse
|
|
|
|
from ...backend import get_bottle_backend, known_backend_names
|
|
from ..constants import PROG
|
|
|
|
|
|
def cmd_backend(args: list[str]) -> int:
|
|
parser = argparse.ArgumentParser(
|
|
prog=f"{PROG} backend",
|
|
description="Set up or check a backend's host prerequisites.",
|
|
)
|
|
parser.add_argument(
|
|
"action",
|
|
choices=("setup", "status", "teardown"),
|
|
help="setup: provision/print host prerequisites; status: report "
|
|
"readiness; teardown: undo setup (uninstall)",
|
|
)
|
|
parser.add_argument(
|
|
"--backend",
|
|
choices=known_backend_names(),
|
|
default=None,
|
|
help="backend to target (default: $BOT_BOTTLE_BACKEND or the host default)",
|
|
)
|
|
ns = parser.parse_args(args)
|
|
|
|
backend = get_bottle_backend(ns.backend)
|
|
if ns.action == "setup":
|
|
return backend.setup()
|
|
if ns.action == "teardown":
|
|
return backend.teardown()
|
|
return backend.status()
|