From 8b6ef7c8d345da2c8985e49954026de0d1e9fbe3 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Wed, 16 May 2018 08:22:30 -0700 Subject: [PATCH] core: EvalWriteOutput handle dynamic pseudo-type This should actually have been caught by !val.IsWhollyKnown, since DynamicVal is always unknown, but something isn't working quite right here and so for now we'll redundantly check also if it's of the dynamic pseudo-type, and then revisit cty later to see if there's a real bug hiding down there. --- terraform/eval_output.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/terraform/eval_output.go b/terraform/eval_output.go index 5ac417d194..c1b501a555 100644 --- a/terraform/eval_output.go +++ b/terraform/eval_output.go @@ -137,7 +137,7 @@ func (n *EvalWriteOutput) Eval(ctx EvalContext) (interface{}, error) { Sensitive: n.Sensitive, Value: valueTyped, } - case !val.IsWhollyKnown(): + case ty == cty.DynamicPseudoType || !val.IsWhollyKnown(): // While we're still using our existing state format, we can't represent // partially-unknown values properly, so we'll just stub the whole // thing out.