Skip to content

Build/Deployment/Run Configuration views + Explorer dock#2

Draft
ChrisonSimtian wants to merge 1 commit into
mainfrom
feature/views-and-run-config
Draft

Build/Deployment/Run Configuration views + Explorer dock#2
ChrisonSimtian wants to merge 1 commit into
mainfrom
feature/views-and-run-config

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Contributor

Draft. Restructures the extension's single Targets view into several collapsible Views, mirrors the build targets into the file Explorer, and adds a Run Configuration form.

What's in it

  • Build view — the target tree, registered in both the ☢️ Fallout container (fallout.build) and the file Explorer (fallout.buildExplorer); one TreeDataProvider, two homes.
  • Deployment view — placeholder; lights up once the framework emits a deployment-graph.json for the ADR-0009 CD flow.
  • Run Configuration — a webview-view form: parameters (workspaceState → --name value args) and secrets (SecretStorage → env vars; values never rendered).
  • Run flow — ▶ applies the saved config silently; Run with Parameters… prompts an InputBox prefilled with the target + saved args.

Scope / relation to #1

Relates to #1. This delivers the Run Configuration view (the vessel); #1's real ask — declaration-driven population (e.g. NuGetApiKey appearing automatically from the build's [Parameter]/[Secret] members) — is not in this PR and stays open. It's blocked on Fallout-build/Fallout#499 (the graph must emit parameters[] first). So this PR does not close #1.

Verify

  • npm run compile clean; new src/runConfig.ts.
  • Load via Extension Development Host against a repo with .fallout/temp/build-graph.json.

Restructure the single Targets view into several collapsible Views in the
Fallout container, and mirror the build targets into the file Explorer.

- Build view: the existing target tree, registered under both fallout.build
  (Fallout container) and fallout.buildExplorer (Explorer dock) — one provider,
  two homes; refresh updates both.
- Deployment view: placeholder pending a deployment-graph.json from the CD model
  (ADR-0009); shows welcome content for now.
- Run Configuration: a webview-view form for parameters (workspaceState → CLI
  args) and secrets (SecretStorage → env vars, values never rendered).
- Run flow: ▶ applies the saved run config silently; "Run with Parameters…"
  prompts an InputBox prefilled with target + saved args before running.

Relates to #1 (this adds the Run Configuration view;
declaration-driven population of params/secrets from the build graph is the
remaining part, blocked on Fallout-build/Fallout#499).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ChrisonSimtian ChrisonSimtian added this to the vscode extension milestone Jul 17, 2026
@ChrisonSimtian ChrisonSimtian added the enhancement New feature or request label Jul 17, 2026
@ChrisonSimtian ChrisonSimtian self-assigned this Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant