Unable to Create Job Task Using Git Provider Invalid Path

[umccanna]

I am attempting to create a task in a job using the Git Provider as a source and GitHub is the provider.  The repo is a private repo.  Regardless of how I enter the path to the notebook I receive the same error that the notebook path is invalid and only absolute paths are supported and must begin with a forward slash (/). 

If I attempt to prefix my path with a forward slash I get an error in the UI that git provider paths must be relative and not begin with forward slash.

I have attempted to wrap the path in quotes and I've tried escaping the spaces with a backslash.  I've also tried prefixing the path with blob/main or this_is_a_repo_name and neither seem to be working.

Has anyone else experienced this?  I can't find an example of the YAML configuration that could be used as an alternative (thinking it may be a UI limitation).

Example of Configuration:
GitHub Repo Path: https://github.com/ExampleAccount/this_is_a_repo_name
Branch: main
Path to Notebook: 00 - Utilities/this_is_a_notebook_name

[filipniziol]

Hi @umccanna ,

how exactly you are trying to create the job?
Are you using databricks asset bundles?

Is your yaml looking like below?

tasks:
  - task_key: ExampleTask
    notebook_task:
      notebook_path: "00 - Utilities/this_is_a_notebook_name" 
    job_cluster_key: ExampleCluster
    git_source:
      git_url: https://github.com/ExampleAccount/this_is_a_repo_name
      git_provider: github
      git_branch: main

[umccanna]

Hey,  

I am creating the job via the UI. 

1. I change the Source dropdown to Git provider
2. Select Add a git reference
3. Fill out the required info
   1. Url: https://github.com/ExampleAccount/this_is_a_repo_name
   2. Provider: GitHub
   3. Reference: main
   4. Hit Save
4. Enter in my relative notebook path of 00 - Utilities/this_is_a_notebook_name
5. Select a Cluster
6. Hit Save task and I see this error message pop up
   

[ad1041]

Any solution to this problem ? I'm too facing the same error.

[umccanna]

Recently this started working for us with no changes on our side.  I'm guessing something was resolved on the Databricks end, but no one notified us of a fix. 

[umccanna · Accepted solution]

Like I said in a previous response.  This started working automatically a few days ago with no changes on our end.  The developer who was working on this decided to try it one more time and it just worked, no error this time.  I don't know if Databricks pushed out a fix or what.