Justin Chadwell cc87bd104e

bake: avoid early-exit for resolution failures ...

With changes made to allow lazy evaluation, we were early exiting if an
undefined name was detected, either for a variable or a function.

This had two key implications:

1. The error messages changed, and became significantly less
   informative.

   For example, we went from:

   > Unknown variable; There is no variable named "FO". Did you mean "FOO"?, and 1 other diagnostic(s)

   To

   > Invalid expression; undefined variable "FO"

2. Any issues in our function detection from funcCalls which cause JSON
   functions to be erroneously detected cause invalid functions to be
   resolved, which causes new name resolution errors.

To avoid the above problems, we can defer the error from an undefined
name until HCL evaluation - which produces the more informative errors,
and does not suffer from incorrectly detecting JSON functions.

Signed-off-by: Justin Chadwell <me@jedevc.com>
(cherry picked from commit dc8a2b03987f1266ace9a7cdcba92f5e4ccdb8ed)

2023-02-08 14:33:53 +01:00

..

body.go

bake: support block-based interpolation

2022-12-13 17:27:39 -08:00

expr.go

bake: support null arg value

2022-12-14 08:29:27 +01:00

hclparser.go

bake: avoid early-exit for resolution failures

2023-02-08 14:33:53 +01:00

stdlib.go

bake: add timestamp function

2022-07-18 11:29:35 +01:00