admin/felhom.eu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(f9): reject recommendation #1 auto-register-on-attach (A3)

Browse Source 
Contradicts the new->enrolled manual-enrollment model; manual enroll is
by design. The additive-discovery sub-point was adopted (controller
v0.64.0 A1) but only for paths deployed apps reference, not auto-register
of agent-attached drives.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
authentik Default Admin
2026-06-14 17:33:33 +02:00
parent 1fd6e1a22f
commit b5a961477d
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/backlog/DIAGNOSIS-f9-storage-registration-gap-2026-06-14.md
+8 -2
View File
@@ -87,12 +87,18 @@ reads as generic but is specifically the OS-disk volume; meanwhile the HDD also
label (e.g. "Belső SSD" for the internal volume vs the drive's own name for the HDD) would remove the ambiguity.
## Recommended fix direction (to spec next — NOT implemented here)
1. **Auto-register on attach (primary).** Make a drive the agent has attached into the guest become a registered
1. ~~**Auto-register on attach (primary).**~~ **REJECTED (2026-06-14)** — contradicts the new→enrolled
manual-enrollment model; manual enroll is by design. A drive becomes usable through the explicit
enroll/"Regisztrálás" flow (recommendation #2), not by auto-registering whatever the agent attached
out-of-band. (The "make discovery additive, not return-if-any-path-exists" sub-point WAS adopted —
shipped in controller v0.64.0, A1 — but only as additive pickup of paths referenced by *deployed apps*,
NOT as auto-register-on-attach.)
~~Make a drive the agent has attached into the guest become a registered
storage path automatically, so F9's attach is usable end-to-end. Options: (a) the controller's startup/periodic
storage reconcile consults the **agent `/disks`** and registers any `guest_attached=true` user-data drive missing
from the registry (extend beyond the app-`HDD_PATH` scan); and/or (b) the enroll/re-assert path that binds a
drive also performs `registerStoragePath`. Also **remove the one-time-seed gate** (or make discovery additive,
not "return if any path exists") so it can pick up drives added after the first run.
not "return if any path exists") so it can pick up drives added after the first run.~~
2. **Keep `handleStorageRegister` as the explicit fallback** ("Regisztrálás" button) for the mounted-but-unregistered
case, and make the "Nem regisztrált" badge clearly actionable. For the **immediate** demo state, this button
(`POST /api/storage/register {where:/mnt/felhom-usb}`) would register felhom-usb + make it selectable — no fix needed to recover now.