Repository navigation
feat(console): show a storage.mode memory banner from /healthz - #185
Merged
Merged
Conversation
Refs #180 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Bugs5382
marked this pull request as ready for review
October 15, 2026 18:47
Contributor
Author
|
Approved. The memory-mode banner. Refs #180 |
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
cryptos-manager#201 added a
storage.modefield to the anonymous/healthzbody so theconsole can warn an operator running
storage.mode: memory. This adds that warning: apersistent banner in the app shell when the manager reports memory storage, naming what is
lost on restart (operator registrations and the manager's own audit log; the CA nodes keep
their own audit chains). It's dismissible for as long as the page stays open, but a reload
asks
/healthzagain and shows it again if the manager still answers memory.Refs #180
Verification
How this was verified
npx vitest runinapps/console(725 tests, including the newhealth.test.tsandmemory-mode-banner.test.tsx, the latter with an axe check)npm run lint(eslint + prettier) at the repo rootnpm run buildat the repo root, thennode scripts/check-release-bundle.mjs apps/console/dist(the release bundle carries no mock fixtures)task license --dry(0/374 files need a header change)No new dependency. No behavior change outside the new banner, so no other docs needed.