mirror of https://github.com/databricks/cli.git
deb062c489
## Changes We didn't return the error upon creating a workspace or account client. If there is an error, it must always propagate up the stack. The result of this bug was that we were setting a `nil` account or workspace client, which in turn caused SIGSEGVs. Fixes #913. ## Tests Manually confirmed this fixes the linked issue. The CLI now correctly returns an error when the client cannot be constructed. The issue was reproducible using a `.databrickscfg` with a single, incorrectly configured profile. |
||
|---|---|---|
| .. | ||
| auth.go | ||
| auth_options.go | ||
| auth_options_test.go | ||
| auth_test.go | ||
| bundle.go | ||
| bundle_test.go | ||
| io.go | ||
| logger.go | ||
| progress_logger.go | ||
| progress_logger_test.go | ||
| root.go | ||
| user_agent.go | ||
| user_agent_command.go | ||
| user_agent_command_test.go | ||
| user_agent_upstream.go | ||
| user_agent_upstream_test.go | ||