A Deployment view in the Fallout container, showing the continuous-delivery model — channels → environments → targets.
Implemented on feature/views-and-run-config (#2) as a placeholder: DeploymentProvider.getChildren() returns [], and the view shows welcome content explaining why.
The blocker
The framework doesn't emit a deployment graph. Verified against the current build-graph.json, whose top-level keys are version, falloutVersion, targets — nothing about channels or environments. The CD model is ADR-0009 territory; this view lights up once a deployment-graph.json exists.
Decision needed before the release
This currently ships a permanently empty view. Two defensible options:
- Ship the placeholder — it advertises the roadmap and the welcome text explains the situation. Costs a dead UI element on first impression.
- Strip it, re-add when the graph lands — cleaner first release. Costs re-doing the registration later, which is small.
Worth deciding deliberately rather than by default, since it's the first thing a new user sees in the container.
Acceptance (if kept)
Depends on #9.
A Deployment view in the Fallout container, showing the continuous-delivery model — channels → environments → targets.
Implemented on
feature/views-and-run-config(#2) as a placeholder:DeploymentProvider.getChildren()returns[], and the view shows welcome content explaining why.The blocker
The framework doesn't emit a deployment graph. Verified against the current
build-graph.json, whose top-level keys areversion,falloutVersion,targets— nothing about channels or environments. The CD model is ADR-0009 territory; this view lights up once adeployment-graph.jsonexists.Decision needed before the release
This currently ships a permanently empty view. Two defensible options:
Worth deciding deliberately rather than by default, since it's the first thing a new user sees in the container.
Acceptance (if kept)
Depends on #9.