From 373889ae2597e1a4e51781d1eb249eb3046a23ea Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Fri, 28 Jul 2023 08:48:15 -0700 Subject: [PATCH] stackeval: Actually use the component block "inputs" argument Due to some carelessness in earlier refactoring, the components block evaluation was evaluating the "inputs" expression but not actually saving its result, causing all components to get planned with all their input variables set to default values (or failing, if there were any required). --- .../stacks/stackruntime/internal/stackeval/component_instance.go | 1 + 1 file changed, 1 insertion(+) diff --git a/internal/stacks/stackruntime/internal/stackeval/component_instance.go b/internal/stacks/stackruntime/internal/stackeval/component_instance.go index 9d2ea0e893..22715438d7 100644 --- a/internal/stacks/stackruntime/internal/stackeval/component_instance.go +++ b/internal/stacks/stackruntime/internal/stackeval/component_instance.go @@ -85,6 +85,7 @@ func (c *ComponentInstance) CheckInputVariableValues(ctx context.Context, phase } expr = result.Expression hclCtx = result.EvalContext + v = result.Value } if defs != nil {