We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Databricks CLI return the following error with version 0.222.0 from a GitHub workflow The same setup and command works with version 0.221.1
Command: databricks bundle deploy --target dev --var="var_name=var_value"
Error:
panic: reflect: call of reflect.Value.Set on zero Value goroutine 1 [running]: reflect.flag.mustBeExportedSlow(..) reflect/value.go:247 .. reflect.flag.mustBeExported(...) reflect/value.go:241 reflect.Value.Set({..}) reflect/value.go:2255 .. github.com/databricks/cli/libs/dyn/convert.toTypedInterface( ...}) github.com/databricks/cli/libs/dyn/convert/to_typed.go:285 .. github.com/databricks/cli/libs/dyn/convert.ToTyped({..}) github.com/databricks/cli/libs/dyn/convert/to_typed.go:50 ..
The text was updated successfully, but these errors were encountered:
Thanks for reporting. Do you happen to have a (default) value configured for this variable in your bundle definition?
Sorry, something went wrong.
Thanks for looking at this, Pieter. Yes, there is a default value but set as empty. Note that this works when I switch to version 0.221.1.
Fixed bundle not loading when empty variable is defined (#1552)
3d2f762
## Changes Fixes #1544 ## Tests Added regression test
Thanks for reporting the issue! The fix has been merged and will be released in the upcoming release this week
andrewnester
Successfully merging a pull request may close this issue.
Databricks CLI return the following error with version 0.222.0 from a GitHub workflow
The same setup and command works with version 0.221.1
Command: databricks bundle deploy --target dev --var="var_name=var_value"
Error:
The text was updated successfully, but these errors were encountered: