Add parametrized unit tests for auth types across host profiles#1357
Merged
hectorcast-db merged 3 commits intomainfrom Apr 13, 2026
Merged
Add parametrized unit tests for auth types across host profiles#1357hectorcast-db merged 3 commits intomainfrom
hectorcast-db merged 3 commits intomainfrom
Conversation
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
Existing unit tests cover Legacy Workspace (LW) and Legacy Account (LA)
profiles. This assumes those are correct and working, and builds on them
to verify that auth resolution also works for the remaining profiles:
- NW (New Workspace): LW + account_id + workspace_id
- NA (New Account): structurally same as LA
- SPOGW (SPOG workspace): unified host + account_id + workspace_id
- SPOGA (SPOG account): unified host + account_id
SPOG profiles use account-level OIDC endpoints (with {account_id}
template), matching real SPOG host metadata behavior.
90 tests covering 16 auth types. Cloud-specific auth types use
appropriate host patterns (Azure for azure-*, GCP for google-*).
Environment-locked types (runtime, runtime-oauth, model-serving,
metadata-service) are only tested on workspace profiles since they
never run at account level. external-browser is excluded (requires
interactive browser flow).
Co-authored-by: Isaac
hectorcast-db
force-pushed
the
stack/unit-test-auth-profiles
branch
from
0912d5d to
155d4eb
Compare
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
Co-authored-by: Isaac
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
hectorcast-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
tanmay-db
approved these changes
Apr 13, 2026
Merged
2 tasks
github-merge-queue bot
pushed a commit
to databricks/databricks-sdk-go
that referenced
this pull request
Apr 15, 2026
## Summary - Adds `config/auth_profiles_test.go` with 165 parametrized subtests covering 12 auth types across 6 host profiles (LW, NW, LA, NA, SPOGW, SPOGA) on AWS, Azure, and GCP - Mirrors [databricks/databricks-sdk-py#1357](databricks/databricks-sdk-py#1357) for the Go SDK - Uses `HostMetadataResolver` to inject host metadata, exercising the full production resolution path including `DiscoveryURL` population - Uses `Loaders: []Loader{noopLoader}` to isolate tests from environment variable contamination ### Profiles tested | Profile | Description | Derivation | |---|---|---| | LW | Legacy Workspace | Baseline | | NW | New Workspace | LW + `account_id` + `workspace_id` | | LA | Legacy Account | Baseline | | NA | New Account | Structurally same as LA | | SPOGW | SPOG workspace | Unified host + `account_id` + `workspace_id` | | SPOGA | SPOG account | Unified host + `account_id` | ### Auth types covered pat, basic, oauth-m2m, databricks-cli, github-oidc, env-oidc, file-oidc, metadata-service, azure-client-secret, azure-cli, github-oidc-azure, azure-devops-oidc ### Not covered (with rationale) - `google-credentials`, `google-id`: `GoogleCredentials.Configure` and `GoogleDefaultCredentials.Configure` call Google SDK functions (`idtoken.NewTokenSource`, `impersonate.IDTokenSource`) that parse real crypto keys and make HTTP calls internally. No seam exists to inject mocks via `HTTPTransport` without refactoring production code. NO_CHANGELOG=true ## Test plan - [x] All 165 new subtests pass locally (`go test ./config/ -run TestProfileAuth`) - [x] Existing tests unaffected (`go test ./config/` passes) This pull request was AI-assisted by Isaac. --------- Signed-off-by: Hector Castejon Diaz <hector.castejon@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tests/test_auth_profiles.pywith 90 parametrized unit tests covering 16 auth types across 6 host profiles (LW, NW, LA, NA, SPOGW, SPOGA){account_id}template, matching real SPOG host metadata behaviorProfiles tested
account_id+workspace_idaccount_id+workspace_idaccount_idAuth types covered
pat, basic, oauth-m2m, databricks-cli, env-oidc, file-oidc, github-oidc, azure-client-secret, azure-cli, github-oidc-azure, azure-devops-oidc, google-credentials, google-id, metadata-service, runtime, runtime-oauth, model-serving
Test plan
NO_CHANGELOG=true
This pull request was AI-assisted by Isaac.