Sluijsens
9ab30fe2a6
Unit suites already passed individually; this is the full solution together plus what none of them could check alone: two real hosts talking to each other, a slave API key encrypted by one process and decrypted by the next one after a restart, and headers landing on actual static files instead of a simulated response.
835 B
Performance Test Instructions
Status: N/A for this feature
requirements.md § 5–6 (Non-Functional Requirements) defines no throughput, latency or concurrent-user
targets for this feature — it is CI/CD and deployment tooling, not a user-facing capacity change.
The one performance-adjacent decision made (TracesSampleRate: 0.1 for Sentry, TunnelMaxPayloadBytes: 204800) is a cost/quota control for observability, not a system performance requirement, and was
already verified during U4's code generation.
If load/throughput requirements are identified later (e.g. for the deploy pipeline's own duration, or
for the public website once real content is deployed into wwwroot/web/), they belong to a
follow-up feature — this deployment-workflow feature does not change the CMS's own runtime capacity
characteristics.