vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-07-09 16:00:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

Extend MSP install proof for portal rollups

Browse source
This commit is contained in:
rcourtman 2026-07-07 20:49:55 +01:00
parent 4382919447
commit 4043c466f6
8 changed files with 422 additions and 89 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/release-control/v6/internal/subsystems/cloud-paid.md
View file

@ -679,6 +679,11 @@ or other self-hosted uncapped continuity plans.
age labels from read-only setup facts so providers can prioritize the
workspace list, but it must not become an alert console or expose alert
bodies, remediation state, acknowledgements, or cross-client alert streams.
Those setup facts must read report schedule counts from the client runtime's
org-scoped `report_schedules.json` store and active-alert counts from the
org-scoped `alerts/active-alerts.json` runtime file before falling back to a
legacy tenant-root active-alert file, because tenant monitors own
org-scoped runtime persistence.
Pulse Account also owns the provider-facing setup progression for client
workspaces: after workspace creation the portal should select the created
workspace, reveal the setup job, and preserve workspace/target context in

8
docs/release-control/v6/internal/subsystems/deployment-installability.md
View file

@ -165,9 +165,11 @@ TLS floor in the dynamic config.
`pulse-control-plane provider-msp proof` must exercise the first-client
onboarding path through workspace creation, client-bound install token
generation, tenant-local unified-agent report ingest, tenant-bound install
token rotation, rotated-out token rejection, handoff exchange, and
duplicate-hostname isolation before provider-hosted MSP installability is
treated as proven. The proof is license-backed by default: `license_file` must be the
token rotation, rotated-out token rejection, handoff exchange,
tenant-runtime report schedule creation, portal-visible active-alert rollup
facts, and duplicate-hostname isolation before provider-hosted MSP
installability is treated as proven. The proof is license-backed by default:
`license_file` must be the
resolved provider MSP plan source unless the operator explicitly opts into
the local-development `--allow-env-plan` escape hatch.
The same proof surface must also keep adversarial client-boundary probes in