Skip to content
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

Skip profile resolution if DATABRICKS_AUTH_TYPE is set #1068

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

pietern
Copy link
Contributor

@pietern pietern commented Dec 15, 2023

Changes

If a user configures a workspace host in a bundle and wants to use the "azure-cli" authentication type, we would still run profile resolution. If the databrickscfg has a matching profile, we still load it, even though it should be a fallback.

Tests

  • Unit test.
  • Manually confirmed that setting DATABRICKS_AUTH_TYPE=azure-cli now works as expected.

If a user configures a workspace host in a bundle and wants to use the
"azure-cli" authentication type, we would still run profile resolution. If the
databrickscfg has a matching profile, we still load it, even though it should
be a fallback.
@pietern pietern added this pull request to the merge queue Dec 18, 2023
Merged via the queue into main with commit b17e845 Dec 18, 2023
4 checks passed
@pietern pietern deleted the skip-host-based-auth-if-auth-type-set branch December 18, 2023 10:02
shreyas-goenka added a commit that referenced this pull request Dec 20, 2023
CLI:
 * Upgrade Go SDK to 0.27.0 ([#1064](#1064)).
 * Skip profile resolution if `DATABRICKS_AUTH_TYPE` is set ([#1068](#1068)).
 * Test existing behavior when loading non-string spark conf values ([#1071](#1071)).
 * Do not allow input prompts in Git Bash terminal ([#1069](#1069)).
 * Added output template for list-secrets command ([#1074](#1074)).
 * Set metadata fields required to enable break-glass UI for jobs ([#880](#880)).
 * Revert using IsPromptSupported from promptOrAssignDefaultValues ([#1077](#1077)).
 * Do not prompt for template values in Git Bash ([#1082](#1082)).

Bundles:
 * **FILL THIS IN MANUALLY BY MOVING RELEVANT ITEMS FROM ABOVE LIST**

Internal:
 * **FILL THIS IN MANUALLY BY MOVING RELEVANT ITEMS FROM ABOVE LIST**

API Changes:
 * Changed `databricks connections update` command with new required argument order.
 * Changed `databricks serving-endpoints update-config` command with new required argument order.
 * Added `databricks serving-endpoints put` command.
 * Removed `databricks account network-policy` command group.

OpenAPI commit 63caa3cb0c05045e81d3dcf2451fa990d8670f36 (2023-12-12)
Dependency updates:
 * Bump github.com/google/uuid from 1.4.0 to 1.5.0 ([#1073](#1073)).
 * Bump golang.org/x/crypto from 0.16.0 to 0.17.0 ([#1076](#1076)).
@shreyas-goenka shreyas-goenka mentioned this pull request Dec 20, 2023
github-merge-queue bot pushed a commit that referenced this pull request Dec 21, 2023
CLI:
* Upgrade Go SDK to 0.27.0
([#1064](#1064)).
* Skip profile resolution if `DATABRICKS_AUTH_TYPE` is set
([#1068](#1068)).
* Do not allow input prompts in Git Bash terminal
([#1069](#1069)).
* Added output template for list-secrets command
([#1074](#1074)).

Bundles:
* Set metadata fields required to enable break-glass UI for jobs
([#880](#880)).
* Do not prompt for template values in Git Bash
([#1082](#1082)).
* Tune output of bundle deploy command
([#1047](#1047)).

API Changes:
* Changed `databricks connections update` command with new required
argument order.
* Changed `databricks serving-endpoints update-config` command with new
required argument order.
 * Added `databricks serving-endpoints put` command.
 * Removed `databricks account network-policy` command group.

OpenAPI commit 63caa3cb0c05045e81d3dcf2451fa990d8670f36 (2023-12-12)

Dependency updates:
* Bump github.com/google/uuid from 1.4.0 to 1.5.0
([#1073](#1073)).
* Bump golang.org/x/crypto from 0.16.0 to 0.17.0
([#1076](#1076)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants