Using the Databricks Repos API to bring Repo in top-level production folder to latest version

george2020 — Fri, 18 Mar 2022 17:22:57 GMT

I am having an issue with Github Actions workflow using the Databricks Repos API. We want the API call in the Git Action to bring the Repo in our Databricks Repos Top-level folder to the latest version on a merge into the main branch.

The Github Actions workflow that we have set up is:

on:
  pull_request:
    types:
      - closed
 
jobs:
  if_merged:
    if: github.event.pull_request.merged == true
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - run: |
          export DATABRICKS_TOKEN=databricks_token_here
          curl PATCH --header "Authorization: Bearer $DATABRICKS_TOKEN" \
          https://<databricks-instance>/api/2.0/repos/{repo_id}?branch=main

Upon merging, the Github Action is successful. But when going back to the Repo in Databricks, the updated files are not there unless we pull in the Databricks Repos UI.

Is there something that I am missing from the Actions workflow?

topic Using the Databricks Repos API to bring Repo in top-level production folder to latest version in Data Engineering

Using the Databricks Repos API to bring Repo in top-level production folder to latest version