Workflow job failing with source as Git Provider (remote github repo) with SP

[srinum89]

Facing issue using Github App when running job with source as "Git provider" using Service Principle. Since we can't use PAT with SP on github, I am using Github app for authentication. 

Followed below documentation but still giving permission issue. 

https://learn.microsoft.com/en-us/azure/databricks/repos/get-access-tokens-from-git-provider

Why use the Databricks GitHub App instead of a PAT? from above link.

[BigRoux]

When running a Databricks workflow with a Git provider source using a Service Principal, you’re encountering permission issues despite using the GitHub App for authentication. This is a common challenge because Service Principals cannot use Personal Access Tokens (PATs) with GitHub.

The core problem is that while the Databricks GitHub App provides several advantages over PATs (OAuth 2.0 authentication, automatic token renewal, and more granular access control), there’s a specific configuration needed for Service Principals to access Git repositories.
Service Principals cannot create tokens like PATs or SSH Keys in GitHub, which creates an authentication challenge when they need to access Git repositories for workflows.

Solutions

1. Configure Git Credentials for the Service Principal

You need to explicitly set up Git credentials for your Service Principal using the Git Credential API:

 - Use the Databricks REST API to add Git credentials for your Service Principal

 - Specify the correct parameters:

     For GitHub, use the appropriate git_provider value

     Include the personal_access_token (this would be a token created by a user with appropriate access)

     Set git_username to the Service Principal’s display name