-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
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
Fix databricks configure
if new profile is specified
#1030
Conversation
…ified The code included the to-be-created profile in the configuration and that triggered the SDK to try and load it. Instead, we must use the specified host and token directly.
@@ -42,7 +42,11 @@ func configureInteractive(cmd *cobra.Command, flags *configureFlags, cfg *config | |||
|
|||
// Ask user to specify a cluster if not already set. | |||
if flags.ConfigureCluster && cfg.ClusterID == "" { | |||
w, err := databricks.NewWorkspaceClient((*databricks.Config)(cfg)) | |||
// Create workspace client with configuration without the profile name set. | |||
w, err := databricks.NewWorkspaceClient(&databricks.Config{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any other fields from cfg
which we might potentially need?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, because we only set Host
and Token
in the rest of the command.
When we do a more involved auth wizard, we should carry over all relevant attributes except the profile.
This is a bugfix release to address issues with v0.210.0. CLI: * Fix `panic: $HOME is not set` ([#1027](#1027)). * Fix `databricks configure` if new profile is specified ([#1030](#1030)). * Filter out system clusters for `--configure-cluster` ([#1031](#1031)). Bundles: * Fixed panic when job has trigger and in development mode ([#1026](#1026)). Internal: * Use `fetch-tags` option in release workflows ([#1025](#1025)).
This is a bugfix release to address issues with v0.210.0. CLI: * Fix `panic: $HOME is not set` ([#1027](#1027)). * Fix `databricks configure` if new profile is specified ([#1030](#1030)). * Filter out system clusters for `--configure-cluster` ([#1031](#1031)). Bundles: * Fixed panic when job has trigger and in development mode ([#1026](#1026)). Internal: * Use `fetch-tags` option in release workflows ([#1025](#1025)).
Changes
The code included the to-be-created profile in the configuration and that triggered the SDK to try and load it. Instead, we must use the specified host and token directly.
Tests
Manually. More integration test coverage tbd.