ate-setup: expose install-microvm-deps.sh as a standalone deploy/delete command
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Look at cmd/ate-setup/deploy_benchmarks.go to see how DeployBenchmarks and DeleteBenchmarks call runScript. The new subcommands will be added in the same command structure, likely in a new file like deploy_microvm_deps.go. The script hack/install-microvm-deps.sh already exists; the task is to wire it up with the existing Config.ScriptEnv(). Check differences.md for context on script vs. Go reimplementation. Test by running the new commands locally.
Written by the indexing model from the issue text.
Description
Problem
Staging the micro-VM assets and applying the cluster-wide microvm SandboxConfig is only reachable as a side effect of deploy benchmarks --sandbox-class=microvm. There is no way to get just the SandboxConfig.
So downstream installers call hack/install-microvm-deps.sh directly (ai-on-gke/substrate-gke#40) and rebuild by hand the env Config.ScriptEnv() already provides — ARCH, ATE_INSTALL_KIND, the snapshot bucket, KUBECTL_CONTEXT.
Proposal
ate-setup deploy microvm-deps # hack/install-microvm-deps.sh --install
ate-setup delete microvm-deps # hack/install-microvm-deps.sh --delete
Two thin subcommands over the runScript call DeployBenchmarks / DeleteBenchmarks already make. Not a Go reimplementation — the script stays a script, per cmd/ate-setup/differences.md.
Unblocks #1503. PR coming.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 473
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 257
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from agent-substrate/substrate
-
kind/docs prio/P2
Difficulty 1/5 Under an hour Newbie friendliness 95/100
agent-substrate/substrate#1986 ·
Maintainers usually reply within 1 day
-
area/demos good first issue kind/docs prio/P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
agent-substrate/substrate#1792 ·
Maintainers usually reply within 1 day
-
area/benchmarking kind/feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agent-substrate/substrate#1750 · 2 comments ·
Maintainers usually reply within 1 day
-
area/node area/observability good first issue kind/feature prio/P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agent-substrate/substrate#1647 · 1 comment ·
Maintainers usually reply within 1 day
-
area/demos kind/bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
agent-substrate/substrate#1579 · 1 comment ·
Maintainers usually reply within 1 day
All issues in agent-substrate/substrate
Similar issues
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jordansmall/spindrift#4146 ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/ibmcloud-volume-file-vpc#119 ·
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
IBM/networking-go-sdk#339 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/mcp-lifecycle-operator#439 ·
Maintainers usually reply within 1 day
-
area: global bug dx priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day