feat(fleet): live mode wiring the FM UI to the manager (read-only)#44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Adds a
VITE_FLEET_MODE(mock | live | live-auth) data-source seam so the Fleet Manager UI can display live data from the manager backend. All surfaces (nodes, certs, profiles, adapters, audit, enrollment) read live via a Connect client inlivemode;mockstays the default and is byte-for-byte unchanged. Also adds a CSPconnect-srcallowance for the local manager origin and guards the topology view against a cold-load crash before the live fetch resolves. Writes stay mock (read-only this phase).Closes #43.
Notes
Third of three PRs; merge order api -> manager -> web. DRAFT / blocked: depends on api#42 + the manager PR. The generated TS client is currently vendored at
src/gen/fleet/as a dev bridge; CI/merge readiness waits on the api TS package being published (the "publish api" follow-up).How verified
106 tests green (mock default unchanged); build/eslint/prettier/license clean. Cold-loaded every surface in a real browser (
livemode) against two real local CryptOS nodes: certs show the real node-issued leaf + sub-CA, topology shows both nodes, catalog surfaces show seeded data, zero CSP/fetch errors; mock mode still renders fixtures.