Expand description
Requirements-flow driver for super::DeployerCredentials.
validate_requirements reads the env, resolves the bound deployer
handler through the registry, runs the handler’s probes, and returns
both a Credentials doc (ready for the caller to persist) and the
RequirementsReport for the CLI envelope.
The runner does NOT write the doc — that’s the caller’s choice (the
rotate verb persists; requirements returns the report and lets the
caller decide). This keeps the runner pure-ish (one store read, no
store write) and lets tests assert the probe output without observing a
filesystem mutation.
Structs§
- Capability
- A single capability the deployer’s credentials must satisfy.
- Capability
Check - Requirements
Report - Result of a full validate run — one entry per capability in the order the handler declared them.
- Validation
Context - Per-call context passed to
super::DeployerCredentials::validate.
Enums§
- Capability
Status - Outcome for one capability probe.
- Validate
Error
Functions§
- validate_
requirements - Drive a
requirementsflow against the env’s bound deployer env-pack.