Closed shreyas-goenka closed 2 weeks ago
Is it worth the effort to deprecate this? At this point it seems easier to continue maintaining this and it likely costs more to deprecate this than to continue supporting it.
If we deprecate this:
@andrewnester Ah I see that we also support the override syntax for complex variables. That gets complex because of the inherent ambiguity of whether it's an override or the full definition. Maybe it makes sense to deprecate this for complex variables, but keep supporting it for primitive?
Note: This PR builds on top of https://github.com/databricks/cli/pull/1700 and has to wait for it.
Changes
This PR aliases and overrides the schema associated with the variables block in
target
to allow for directly specifying a variable value in the JSON schema (without an levels of nesting). This is needed because this direct value is resolved by dynamically parsing the configuration tree. https://github.com/databricks/cli/blob/ca6332a5a4325aff1be848536f45d13bd74d93b3/bundle/config/root.go#L424Tests
Existing unit tests.