mirror of https://github.com/databricks/cli.git
5f59572cb3
## Changes When resolving a value returned by the lookup function, the code would call into `resolveRef` with the key that `resolveKey` was called with. In doing so, it would cache the _new_ ref under that key. We fix this by caching ref resolution only at the top level and relying on lookup caching to avoid duplicate work. This came up while testing #1098. ## Tests Unit test. |
||
|---|---|---|
| .. | ||
| lookup.go | ||
| lookup_test.go | ||
| ref.go | ||
| ref_test.go | ||
| resolve.go | ||
| resolve_test.go | ||