Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non admin users cannot view runs of local notebooks after the tmp notebook is deleted #50

Open
WillItUsername opened this issue Dec 4, 2023 · 2 comments

Comments

@WillItUsername
Copy link

When running local notebooks you need workspace-temp-dir. The notebook is uploaded to the temp dir, is then run and after the run is deleted. After this, the access-control-list-json no longer allows the users of the group to see the run, only workspace admins can see the run. If you as a user of the groups who are allowed access in the access-control-list-json try to access it you get the following error:

image

If I add admin privileges to the user as the error says, I can indeed view the notebook run.
The users in the group can also view the run while the notebook is not yet deleted from the workspace-temp-dir directory.

Is there no way of allowing users/groups to view a run of a temp notebook without giving them admin privileges?

Below is the yml and all the parameters used. It was run on Azure Databricks.

 - name: Run Notebook on Dev
      uses: databricks/run-notebook@v0
      with:
        databricks-host: https://adb-XXXXXXXXXXXXXXXX.X.azuredatabricks.net/
        databricks-token: ${{ env.DATABRICKS_TOKEN_DEV }}
        local-notebook-path: d_notebook.sql
        workspace-temp-dir: /some-workspace-dir/tmp
        new-cluster-json: >
          {
            "num_workers": 1,
            "spark_version": "13.3.x-scala2.12",
            "node_type_id": "Standard_DS3_v2"
          }
        access-control-list-json: > 
          [
            {
              "group_name":"DataEngineer",
              "permission_level":"CAN_MANAGE"
            },
            {
              "group_name":"DataModeler",
              "permission_level":"CAN_VIEW"
            }
          ]
@veer-bhansari
Copy link

Hi @WillItUsername , I am facing the same.
Have you found out any resolution?
Commenting to follow.

@WillItUsername
Copy link
Author

No, but since this action is just a wrapper on the API, it's probably not a problem with the action, and just how the API/Databricks behaves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants