pub fn stored_input_values(
inputs: &[StackInputDefinition],
values: &HashMap<String, Value>,
environment: &EnvironmentVariablesSnapshot,
) -> HashMap<String, Value>Expand description
The deployment’s input values as the deployer secret helpers must see them.
A control plane never puts a stored secret’s value in input_values: it
delivers it through the environment variables the input maps. Such an
input counts as stored when every variable it maps is in environment, so
a developer value is not mistaken for an empty deployer slot. Input and
user variable names are unique, so a mapped name can only come from the
input. The added entries mark presence only and carry no value.