Repository navigation
Run Configuration: populate parameters & secrets from the build's declarations #1
Description
Problem
The extension's Run Configuration view is free-form — it only shows params/secrets you hand-type. Declared members like NuGetApiKey ([Parameter][Secret]) don't appear, so the Secrets section looks empty.
Blocked on Fallout-build/Fallout#499 (the framework graph must emit parameters[] first).
Outcome
Run Configuration reads parameters[] from build-graph.json and pre-populates:
- non-secret params → Parameters rows (fill value → CLI args)
[Secret]params → Secrets rows, shown "not set" until a value is entered (→ SecretStorage → env var on run)
Acceptance criteria
NuGetApiKeyand peers appear automatically after a build/plan.- Declared secrets read "not set" until set; values live in SecretStorage, applied as env vars on run.
- Values still flow to runs as today (params → args, secrets → env); free-form add still works for extras.
- Graceful when the graph has no
parameters[](older builds) — falls back to today's free-form behaviour.
Activity
Add Build/Deployment/Run Configuration views and an Explorer dock
ChrisonSimtian commentedon Aug 22, 2026
Still blocked, and labelled
blockednow so it's visible without opening the issue.Checked against
developtoday: the #15–#20 stack shipped the Run Configuration view (#18 parameters, #19 secrets via SecretStorage, #20 apply-on-run), so it's easy to assume this went with it. It didn't — that work is the free-form half.src/model.tsstill has no notion of parameters, because the graph doesn't carry any.Fallout-build/Fallout#499 is open. Commented there to flag this as a waiting consumer and to spell out which fields are needed (name, secret flag, and description/type/default if cheap).
Unblocks the moment
parameters[]appears inbuild-graph.json; the fallback path in the acceptance criteria means no framework-version coordination is needed.