pub fn signed_deployer_env(
body: &ReleaseBody,
workload: &str,
config_inputs: &BTreeMap<String, Value>,
deployer_values: &HashMap<String, Value>,
) -> Result<BTreeMap<String, String>>Expand description
The env a workload takes from the release’s deployer inputs, resolved the way the cloud
controllers resolve it: the install’s stored value, else the input’s signed default; left
out when the input is optional, has neither, or does not apply (its signed when is off
for the install’s gate values). A required input that applies and has neither is refused.
Only values come from the install’s store (deployer_values); which inputs exist, apply,
are required or have defaults is all signed. config_inputs are the signed config’s
developer input values, which decide when for inputs that name a developer input.
Secret mappings are not here: their values are never signed or sent.