You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Test-only env vars read by shipped binaries: hide or document #1006
Shipped binaries read PLOYZ_INGRESS_VERIFY_PORT, the health-monitor period, SSH control-persist, the upgrade release dir and the ACME directory. Once the 1.0 CLI cut lands, which of these survive? For each survivor: does it move behind a test seam, or does it become a documented operator knob?
After the 1.0 CLI cut, one of the five survives. It becomes a documented operator knob. The other four are deleted.
Env var
Read by
Disposition
PLOYZ_ACME_DIRECTORY
daemon certificates
Keep, documented in core/README.md: unset = Let's Encrypt production, a URL = that ACME directory, empty = issuance off. The rung-4 testkit keeps using the empty state.
Deleted as one chain. Its only production user was qualification, which is already deleted. ReleaseSource::Local leaves the stored upgrade receipt and remains only in #[cfg(test)] for the in-process installer tests. The setup_cli.rs tests move in-process and pass the bootstrap in directly.
Activity
nick-potts commentedon Sep 24, 2026
Resolution
After the 1.0 CLI cut, one of the five survives. It becomes a documented operator knob. The other four are deleted.
PLOYZ_ACME_DIRECTORYcore/README.md: unset = Let's Encrypt production, a URL = that ACME directory, empty = issuance off. The rung-4 testkit keeps using the empty state.PLOYZ_INGRESS_VERIFY_PORTdns/probe.rsdnsmodule (Remove Hosted DNS from the daemon, SDK and CLI).PLOYZ_SSH_CONTROL_PERSISTconnect.rsControlPersist=10mbecomes a constant. Its only setter wasbuild_layer3, which runsployz deploy.PLOYZ_HEALTH_MONITOR_PERIODupdate.monitorin the Deploy Intent is the only control. Tests set that or wait the default 5s.PLOYZ_RELEASE_DIR,ployzd install --release-dir,PLOYZ_UPGRADE_RELEASE_DIRReleaseSource::Localleaves the stored upgrade receipt and remains only in#[cfg(test)]for the in-process installer tests. Thesetup_cli.rstests move in-process and pass the bootstrap in directly.Execution: Remove test-only env vars from shipped binaries; document PLOYZ_ACME_DIRECTORY