Prepare v6.0.0 release candidate

Tighten v5-to-v6 upgrade safety, release installability, provider MSP mode handling, AI cost accounting, metrics flushing, and frontend guardrails for the v6.0.0 GA candidate.
This commit is contained in:
rcourtman 2026-06-04 14:07:14 +01:00
parent a73a24259c
commit bd6f77e093
119 changed files with 4753 additions and 2046 deletions

View file

@ -1,4 +1,7 @@
# Domain
# Client runtimes are routed as https://<client-id>.${DOMAIN}/.
# Provider-hosted MSP: use the MSP's own domain, for example pulse.example-msp.com.
# Pulse-hosted MSP: use a Pulse-operated provider namespace, for example example-msp.msp.pulserelay.pro, and set CP_CONTROL_PLANE_MODE=pulse_hosted_msp.
DOMAIN=msp.example.com
ACME_EMAIL=admin@example.com
@ -13,6 +16,7 @@ CP_PULSE_IMAGE=ghcr.io/rcourtman/pulse@sha256:<pin>
# Control plane
CP_ENV=production
CP_CONTROL_PLANE_MODE=provider_hosted_msp
CP_ADMIN_KEY=
PULSE_PROVIDER_MSP_DATA_DIR=/data
PULSE_PROVIDER_MSP_DOCKER_NETWORK=pulse-provider-msp

View file

@ -53,7 +53,7 @@ services:
environment:
- CP_DATA_DIR=${PULSE_PROVIDER_MSP_DATA_DIR:-/data}
- CP_ENV=${CP_ENV}
- CP_CONTROL_PLANE_MODE=provider_hosted_msp
- CP_CONTROL_PLANE_MODE=${CP_CONTROL_PLANE_MODE:-provider_hosted_msp}
- CP_BIND_ADDRESS=0.0.0.0
- CP_PORT=8443
- CP_ADMIN_KEY=${CP_ADMIN_KEY}