Repository navigation
fix(configurator): show Assistant beside Application template drafts - #170
Conversation
|
Dev acceptance completed successfully at source d3049ac: https://github.com/stackitcloud/stackit-landing-zone/actions/runs/40385230856. The exact release passed all 378 browser tests. The existing configuration chat is visible in Application Landing Zones → Template drafts for an opened platform draft, with the same saved configuration row ID/conversation and explicit local acceptance/save semantics. Application Owner isolation and navigation rehydration were covered by the new desktop/mobile regression. Independent runtime verification confirmed actual App/droplet/source alignment, the new template Assistant UI marker, HTTP 401 for the unauthenticated configuration Assistant endpoint, Assistant enabled and exactly one matching live warm Runner. Migration/access/quota guards and existing recovery/follow-up Apply evidence remain intact. The route-free privileged diagnostic app was deleted. Read-only backend verification confirmed unchanged serial 7, 12 managed resources, preserved identities and a free lock; no customer infrastructure Plan/Apply, State write or lock change was performed. Deployment took 17:45. Build took 21:20: the native lane passed in 165 seconds and all 378 browser tests in 4.8 minutes, but external Ubuntu dependency downloads added 11m36s for 21.3 MB. The bounded CI timeout adjustment retains all acceptance checks under such provisioning delays. No new live-model qualification is claimed; this is the authorized Dev-only UI release with runtime Assistant active. |
Application Landing Zone template drafts were editable in the Application area, but their existing configuration Assistant was only visible in the configuration editor. The Template drafts tab now shows the same chat above the template editor, with a localized explanation of its shared platform configuration context.
The existing saved configuration binding, root draft, conversation endpoint and acceptance callback are reused. Only one chat instance is mounted. Proposals require explicit selection/acceptance, remain local until save, and do not publish or authorize execution. Application Owners cannot see this platform configuration chat. Assistant facts, inference APIs and proposal capabilities are unchanged; no new live-model qualification is claimed for this UI placement.
Validation: complete app check passed (1,258 tests, 76 existing gated skips); final desktop/mobile owner-flow and configurator run passed 170/170, including distinct document/database IDs, proposal vs acceptance vs save, Editor↔Template drafts conversation rehydration without another model POST, and Application Owner isolation. Independent review found no issue. An initial local browser run had one fork-restore failure while a concurrent local build was running; that isolated case passed 2/2 and the subsequent complete 170-case run without concurrent builds passed. No assertions were weakened. EN/DE documentation updated.
The first GitHub application check hit its 15-minute limit while provisioning the browser: Azure Ubuntu OS packages took 11m39s for 24 MB (34 KB/s), before browser acceptance could begin. The application job now has a bounded 25-minute budget, matching the release build; all tests remain required. Workflow lint passed.
Dev release is authorized with dev-skip-assistant-qualification, runtime Assistant active and runner_pool_size=1. No customer infrastructure Plan/Apply or State changes.