mirror of https://github.com/databricks/cli.git
068c7cfc2d
## Changes With https://github.com/databricks/cli/pull/1507 and https://github.com/databricks/cli/pull/1511 we are clarifying the semantics associated with `dyn.InvalidValue` and `dyn.NilValue`. An invalid value is the default zero value and is used to signals the complete absence of the value. A nil value, on the other hand, is a valid value for a piece of configuration and signals explicitly setting a key to nil in the configuration tree. In keeping with that theme, this PR returns `dyn.InvalidValue` instead of `dyn.NilValue` at error sites. This change is not expected to have a material change in behaviour and is being done to set the right convention since we have well-defined semantics associated with both `NilValue` and `InvalidValue`. ## Tests Unit tests and integration tests pass. Also manually scanned the changes and the associated call sites to verify the `NilValue` value itself was not being relied upon. |
||
|---|---|---|
| .. | ||
| tfdyn | ||
| apply.go | ||
| check_running_resources.go | ||
| check_running_resources_test.go | ||
| convert.go | ||
| convert_test.go | ||
| destroy.go | ||
| dir.go | ||
| import.go | ||
| init.go | ||
| init_test.go | ||
| interpolate.go | ||
| interpolate_test.go | ||
| load.go | ||
| load_test.go | ||
| pkg.go | ||
| pkg_test.go | ||
| plan.go | ||
| state_pull.go | ||
| state_pull_test.go | ||
| state_push.go | ||
| state_push_test.go | ||
| state_test.go | ||
| unbind.go | ||
| util.go | ||
| util_test.go | ||
| write.go | ||