gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-10 10:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix tenant-scoped service discovery execution

Browse Source
This commit is contained in:
rcourtman
2026-08-10 19:53:08 +01:00
parent b2dd6abfd8
commit dfcfe3fbd1
4 changed files with 72 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-control/v6/internal/subsystems/ai-runtime.md
+8
View File
@@ -5198,6 +5198,14 @@ single-resource discovery, and `pulse_discovery` refreshes before any
`discovery_interval_hours: 0` is the only manual-command-scan mode: recurring
scans stay stopped, but explicit admin-triggered refreshes may use the
hardcoded trusted catalog.
Each per-organization AI service now passes its organization-pinned
`AgentServer` interface directly into `internal/ai/discovery_adapter.go`.
Deep discovery does not recover the concrete global `agentexec.Server` or
silently drop command execution when the runtime supplies an
`agentexec.OrganizationServer`; connected-agent lookup and command dispatch
therefore remain on the same tenant-scoped view. The interface-backed service
regression in `internal/ai/service_test.go` requires a real deep-discovery run
to dispatch the trusted probe catalog and retain its command evidence.
The value boundary for keeping Discovery is observed workload context:
Assistant and Patrol may consume normalized service name, version, endpoint,
port, config path, data path, log path, bind-mount, confidence, and user-note