Conversation
Authenticates the request identity with a Databricks OAuth service principal (Authorization header) and passes a Google Cloud access token through the X-Databricks-GCP-SA-Access-Token header, so GCP account-level provisioning APIs (e.g. workspace / VPC-endpoint / customer-managed-key creation) can be called with a Databricks-governed identity when SSO is enabled and Google ID token auth is disabled. Reuses the existing serviceToServiceVisitor: the Databricks OAuth token (extracted into databricksOAuthTokenSource) is the primary, and a Google cloud-platform access token (from google_credentials or google_service_account) is the secondary. Selected explicitly via AuthType "oauth-m2m-gcp", since it combines the oauth and google credential groups that the single-auth-method check otherwise rejects. Co-authored-by: Isaac
|
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. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. If this PR is still relevant, please leave a comment or push new changes to keep it open. Thank you for your contributions. |
github-actions
Bot
added
the
stale
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
1 participant
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.
Authenticates the request identity with a Databricks OAuth service principal (Authorization header) and passes a Google Cloud access token through the X-Databricks-GCP-SA-Access-Token header, so GCP account-level provisioning APIs (e.g. workspace / VPC-endpoint / customer-managed-key creation) can be called with a Databricks-governed identity when SSO is enabled and Google ID token auth is disabled.
Reuses the existing serviceToServiceVisitor: the Databricks OAuth token (extracted into databricksOAuthTokenSource) is the primary, and a Google cloud-platform access token (from google_credentials or google_service_account) is the secondary. Selected explicitly via AuthType "oauth-m2m-gcp", since it combines the oauth and google credential groups that the single-auth-method check otherwise rejects.
Co-authored-by: Isaac
Summary
Why
What changed
Interface changes
Behavioral changes
Internal changes
How is this tested?