Skip to main content

signed_deployer_secrets

Function signed_deployer_secrets 

Source
pub fn signed_deployer_secrets(
    body: &ReleaseBody,
    workload: &str,
    config_inputs: &BTreeMap<String, Value>,
    deployer_values: &HashMap<String, Value>,
) -> Result<Vec<DeployerSecretEnv>>
Expand description

The deployer secrets workload reads from the install’s own deployer-secrets vault when it starts, from the signed stack alone: every secret input the deployer provides that applies and maps to the workload, in signed order. Whether a value exists is the vault’s answer when the workload starts (a required one that is missing stops it, an optional one is left unset), so nothing here reads the store. The control plane’s own list adds the secret store’s version of each value, which only restarts a workload on a rotation; this one has none, so a rotated value is read by the next start. A secret input only the developer provides has no value on a protected install and is not here.