feat: expose process administration - #40
Conversation
Provide an authorization-guarded process query through the runtime database adapter so operators can inspect live and stale rows without opening a competing SQLite connection. Keep the polling warning evidence-based and document rolling-deployment overlap.
Greptile SummaryThe PR exposes authorization-guarded process inspection through
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Reviews (2): Last reviewed commit: "fix: freeze process metadata" | Re-trigger Greptile |
Deep-freeze metadata returned by process administration so nested values cannot mutate a published snapshot. Add a regression test for nested mutation.
|
The one review finding on this PR was already fixed by Nested metadata remains mutable (P1)Fixed at head. metadata: Serialization.readonly_copy(process_record.metadata),and Confirmed by running the exact mutation the finding described against this branch:
Nothing else is outstanding: Greptile is at 5/5 with "no blocking failure remains", and this was the only review thread. |
Summary
SolidObjects.administration.processesfor authorized process inspection0.13.2to match the Node packageRoot cause
The polling-only warning is evidence-based.
ProcessRegistryonly emits it when a live process row has a different hostname or PID. Component rows in one Ruby process do not trigger it; a rolling deployment or recently uncleanly stopped process can legitimately remain live during the configured heartbeat window.The administration query gives operators a supported, authorization-guarded way to inspect those rows without opening a competing SQLite connection.
Verification
bundle exec rake— 521 runs, 1,742 assertions, 0 failures/errors, 15 skips