Expand description
Operator-side cloud prepare (§4): shallow git checkout + run a command on
the operator’s machine. Cloud substrates call this and map the neutral
PrepareFailure to their own PrepareFailed-style fault.
Structs§
- Prepare
Failure - A prepare step that failed, as neutral data the provider maps to its own fault (preserving per-provider error codes and remediation).
- Prepare
Plan - A resolved prepare step: the command, the pinned source, and the fully
interpolated env it runs with.
resolve_prepare_envreturnsNonewhen the service declares nopreparehook.
Functions§
- resolve_
prepare_ env - Resolve a service’s prepare env against
namespaceand inject same-named secrets. The caller builds the namespace — substrates differ in what it carries (only Render exports the external-DB url) — so this stays pure and substrate-agnostic. Any failure is the neutralPrepareFailure. - run_
prepare_ command - Shallow-clone
repo@referenceinto a temp dir, runcommandthere withenv, and clean up. Any failure is returned as aPrepareFailure. - run_
service_ prepare - Resolve and run a service’s prepare hook on the operator’s machine. A no-op
when the service declares no
prepare. The caller maps the neutralPrepareFailureto its own fault.