mirror of https://github.com/databricks/cli.git
f7d4b272f4
## Changes Currently, there are a number of issues with the non-happy-path flows for token refresh in the CLI. If the token refresh fails, the raw error message is presented to the user, as seen below. This message is very difficult for users to interpret and doesn't give any clear direction on how to resolve this issue. ``` Error: token refresh: Post "https://adb-<WSID>.azuredatabricks.net/oidc/v1/token": http 400: {"error":"invalid_request","error_description":"Refresh token is invalid"} ``` When logging in again, I've noticed that the timeout for logging in is very short, only 45 seconds. If a user is using a password manager and needs to login to that first, or needs to do MFA, 45 seconds may not be enough time. to an account-level profile, it is quite frustrating for users to need to re-enter account ID information when that information is already stored in the user's `.databrickscfg` file. This PR tackles these two issues. First, the presentation of error messages from `databricks auth token` is improved substantially by converting the `error` into a human-readable message. When the refresh token is invalid, it will present a command for the user to run to reauthenticate. If the token fetching failed for some other reason, that reason will be presented in a nice way, providing front-line debugging steps and ultimately redirecting users to file a ticket at this repo if they can't resolve the issue themselves. After this PR, the new error message is: ``` Error: a new access token could not be retrieved because the refresh token is invalid. To reauthenticate, run `.databricks/databricks auth login --host https://adb-<WSID>.azuredatabricks.net` ``` To improve the login flow, this PR modifies `databricks auth login` to auto-complete the account ID from the profile when present. Additionally, it increases the login timeout from 45 seconds to 1 hour to give the user sufficient time to login as needed. To test this change, I needed to refactor some components of the CLI around profile management, the token cache, and the API client used to fetch OAuth tokens. These are now settable in the context, and a demonstration of how they can be set and used is found in `auth_test.go`. Separately, this also demonstrates a sort-of integration test of the CLI by executing the Cobra command for `databricks auth token` from tests, which may be useful for testing other end-to-end functionality in the CLI. In particular, I believe this is necessary in order to set flag values (like the `--profile` flag in this case) for use in testing. ## Tests Unit tests cover the unhappy and happy paths using the mocked API client, token cache, and profiler. Manually tested --------- Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com> |
||
|---|---|---|
| .. | ||
| autoload_git | ||
| basic | ||
| bundle_permissions | ||
| conflicting_resource_ids | ||
| environment_overrides | ||
| environments_autoload_git | ||
| environments_job_and_pipeline | ||
| environments_override_job_cluster | ||
| git_branch_validation | ||
| include_default | ||
| include_invalid | ||
| include_multiple | ||
| include_with_glob | ||
| interpolation | ||
| interpolation_target | ||
| job_and_pipeline | ||
| job_cluster_key | ||
| job_with_spark_conf | ||
| model_serving_endpoint | ||
| override_job_cluster | ||
| override_job_tasks | ||
| override_pipeline_cluster | ||
| override_sync | ||
| override_sync_no_root | ||
| path_translation | ||
| pipeline_glob_paths | ||
| python_wheel | ||
| registered_model | ||
| relative_path_translation | ||
| relative_path_with_includes | ||
| run_as | ||
| target_empty | ||
| target_overrides | ||
| variables | ||
| yaml_anchors | ||
| yaml_anchors_separate_block | ||
| README.md | ||
| basic_test.go | ||
| bundle_permissions_test.go | ||
| conflicting_resource_ids_test.go | ||
| enviroment_key_test.go | ||
| environment_git_test.go | ||
| environment_overrides_test.go | ||
| environments_job_and_pipeline_test.go | ||
| environments_override_job_cluster_test.go | ||
| git_test.go | ||
| include_test.go | ||
| interpolation_test.go | ||
| job_and_pipeline_test.go | ||
| job_cluster_key_test.go | ||
| job_with_spark_conf_test.go | ||
| loader.go | ||
| model_serving_endpoint_test.go | ||
| override_job_cluster_test.go | ||
| override_job_tasks_test.go | ||
| override_pipeline_cluster_test.go | ||
| override_sync_test.go | ||
| path_translation_test.go | ||
| pipeline_glob_paths_test.go | ||
| python_wheel_test.go | ||
| registered_model_test.go | ||
| relative_path_translation_test.go | ||
| relative_path_with_includes_test.go | ||
| run_as_test.go | ||
| suggest_target_test.go | ||
| sync_include_exclude_no_matches_test.go | ||
| target_empty_test.go | ||
| target_overrides_test.go | ||
| variables_test.go | ||
| yaml_anchors_test.go | ||
README.md
Bundle configuration tests
Every test here uses an example bundle configuration. Each bundle configuration is located in a dedicated subdirectory.