Skip to content

Run Configuration: populate parameters & secrets from the build's declarations #1

Open
Open
Run Configuration: populate parameters & secrets from the build's declarations#1
Labels
blockedExternally blocked; cannot proceed until a dependency landsenhancementNew feature or request
Milestone
vscode extension

Description

@ChrisonSimtian
ChrisonSimtian
opened on Jul 17, 2026

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

  • NuGetApiKey and 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

  1. ChrisonSimtian
    added this to the vscode extension milestone on Jul 17, 2026
  2. ChrisonSimtian
    added
    enhancementNew feature or request
    on Jul 17, 2026
  3. ChrisonSimtian
    transferred this issue fromFallout-build/Fallouton Jul 17, 2026
  4. ChrisonSimtian
    added a commit that references this issue on Aug 14, 2026

    Add Build/Deployment/Run Configuration views and an Explorer dock

    0965734
  5. ChrisonSimtian
    added
    blockedExternally blocked; cannot proceed until a dependency lands
    on Aug 22, 2026

  6. ChrisonSimtian commented on Aug 22, 2026

    @ChrisonSimtian
    ChrisonSimtian
    on Aug 22, 2026
    ContributorAuthor

    Still blocked, and labelled blocked now so it's visible without opening the issue.

    Checked against develop today: 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.ts still 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 in build-graph.json; the fallback path in the acceptance criteria means no framework-version coordination is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedExternally blocked; cannot proceed until a dependency landsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions