mirror of https://github.com/databricks/cli.git
07c4c90772
## Changes `databricks configure` creates a new .databrickscfg if one doesn't already exist, but `databricks auth login` fails in this case. Because `databricks auth login` anyways writes out the config file, we gracefully handle this error and continue. ## Tests Unit test. ``` $ ls ~/.databrickscfg* /Users/miles/.databrickscfg.bak $ ./cli auth login Databricks Profile Name: test Databricks Host: https://<HOST> Profile test was successfully saved $ ls ~/.databrickscfg* /Users/miles/.databrickscfg /Users/miles/.databrickscfg.bak $ cat ~/.databrickscfg ; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified. [DEFAULT] [test] host = https://<HOST> auth_type = databricks-cli ``` |
||
---|---|---|
.. | ||
account | ||
api | ||
auth | ||
bundle | ||
configure | ||
fs | ||
labs | ||
root | ||
sync | ||
version | ||
workspace | ||
cmd.go |