From 3466f0e337a42453e9b8d5130cc639aff4ca29f4 Mon Sep 17 00:00:00 2001 From: Aditya Shantanu Date: Wed, 2 Sep 2026 10:39:58 -0700 Subject: [PATCH] commands.md: the hack/install-demo-*.sh scripts still exist The closing paragraph claimed the per-demo hack scripts are gone, but hack/install-ate.sh still sources hack/install-demo-*.sh and generates its --deploy-demo-NAME / --delete-demo-NAME flags from them. Describe the two installers as parallel instead of declaring one dead. --- cmd/ate-setup/commands.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/cmd/ate-setup/commands.md b/cmd/ate-setup/commands.md index 0506efd3a..99d1b26ed 100644 --- a/cmd/ate-setup/commands.md +++ b/cmd/ate-setup/commands.md @@ -173,6 +173,7 @@ The demo list is not hard-coded here — it is built from the registry in `go run ./cmd/ate-setup deploy demo --help` is authoritative for both the list and the per-demo flags. -Each demo previously had its own `hack/install-demo-*.sh`, sourced by the -installer, which registered the flags above. Those scripts are gone; the demos -now live in [`internal/demos`](internal/demos). +The demos also each have a `hack/install-demo-*.sh`, sourced by +`hack/install-ate.sh`, which registers `--deploy-demo-NAME` / +`--delete-demo-NAME` flags on that installer. ate-setup does not use those +scripts; its demos live in [`internal/demos`](internal/demos).