mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
rcourtman
9d9f13e7b0
The evaluation mode added earlier today was hollow. An unlicensed control plane starts, but release-build client runtimes only trust entitlement leases chained to a Pulse-signed licence, so its client workspaces ran without the capabilities the provider was evaluating. Standing the stack up proved the portal and the isolation boundary and nothing else. setup.sh now requests a capped evaluation licence from the licence server when no licence path is set, sending only the public half of the key it generated locally. It degrades rather than blocks: a missing key, an unreachable server, or a licence-free response leaves the install unlicensed with an explicit warning, an existing licence on disk is reused, and PULSE_PROVIDER_MSP_SKIP_EVAL_LICENSE skips it for air-gapped hosts. Guarded with an if-test rather than a trailing true inside the command substitution, because the derive helper calls die and exit in a subshell is not a status that can be caught, so setup.sh aborted under set -e. Second fix. The lease capability ceiling was selected by licence presence, so an unlicensed provider control plane fell through to the Pulse-hosted branch and minted leases claiming relay, mobile and push, which a provider deployment cannot serve and which previously caused repeating relay registration failures in client runtimes. The ceiling now follows hosting via SetProviderHosted. providerChained keeps its narrower meaning of having a licence available to embed. Third. Corrects a sentence I wrote into cloud-paid.md this afternoon claiming msp_eval carries the same MSP capabilities. A plan version selects the workspace cap; it does not entitle a workspace. The regression test was negative-tested by reverting the ceiling selector and confirming it catches relay. All three setup.sh degradation paths were exercised directly. Licence server side is pulse-pro 7f6a319 and is not live until the next deploy-license-server run.