Open
Description
Describe the issue
DABs only correctly set permissions on the first deployment. Any subsequent redeployment does not update the permission mapping.
Applies to both top-level permission mapping in databricks.yaml and resource-level permissions.
Steps to reproduce the behavior
- Initial job is deployed correctly with applied permission mapping.
- Permission mapping is changed (see below)
- New bundle deployment is successful
- .bundle files on Workspace correctly show the latest version which includes new permissions but the job itself is not updated.
#databricks.yaml - INITIAL DEPLOYMENT
...
targets:
...
master:
mode: production
workspace:
...
permissions:
- user_name: user@example.com
level: CAN_MANAGE#databricks.yaml - CHANGE PERMISSIONS
...
targets:
...
master:
mode: production
workspace:
...
permissions:
- user_name: user@example.com
level: CAN_MANAGE
- group_name: MY_GROUP_NAME
level: CAN_MANAGEExpected Behavior
Permissions are updated on each bundle deployment.
Actual Behavior
No change in permissions after redeployment of DABs.
OS and CLI version
ubuntu-latest and cli latest: databricks/setup-cli@main
CLI version: v0.254.0