โ11-12-2021 11:01 AM
We want to use the REPO directory in our production environment only and have a dev environment with less restrictions. If I use the checkbox on the group admin screen to disable workspace access, it locks out the entire Data Engineering section.
โ11-24-2021 09:04 AM
So I found a way to get 85% of the way there:
1) Disable workspace access for the users group.
2) Create a new group or use another group that you created for the next step.
3) Go to the workspace and right click on whitespace in the root directory.
4) Add the new group/existing group with Read access.
This locks it so that new files can't be created or edited but the exception is the user's personal folder.
The permissions for that are greyed out and can't be changed.
So I proposed an idea to either have the ability to turn off personal folders or to modify the permissions.
see: https://feedback.azure.com/d365community/idea/70547d9f-464d-ec11-a819-0022484e8090
โ11-13-2021 11:52 AM
@Christopher Shehuโ - Hello again! Thank you for this question. It sounds like an interesting one!
โ11-15-2021 06:01 AM
Hi @Christopher Shehuโ Could you please check the below doc and let me know if it helps?
https://docs.databricks.com/repos.html#control-access-to-databricks-repos
โ11-23-2021 10:53 PM
โ11-24-2021 05:23 AM
Thanks for the answers but I'm looking more for something where you can disable the folder structure and ONLY have a git repo in the databricks PRD environment. That way someone can't bypass the github process to create something in prod.
โ11-24-2021 05:27 AM
I don't think that is possible as a user has always access to his own home folder.
Maybe you can think in another direction, like no access at all on production or user groups or restriction in cluster permissions?
โ11-24-2021 05:30 AM
Yeah, that's the conclusion I came to but was hoping I was wrong. Thanks!
โ11-24-2021 09:04 AM
So I found a way to get 85% of the way there:
1) Disable workspace access for the users group.
2) Create a new group or use another group that you created for the next step.
3) Go to the workspace and right click on whitespace in the root directory.
4) Add the new group/existing group with Read access.
This locks it so that new files can't be created or edited but the exception is the user's personal folder.
The permissions for that are greyed out and can't be changed.
So I proposed an idea to either have the ability to turn off personal folders or to modify the permissions.
see: https://feedback.azure.com/d365community/idea/70547d9f-464d-ec11-a819-0022484e8090
Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโt want to miss the chance to attend and share knowledge.
If there isnโt a group near you, start one and help create a community that brings people together.
Request a New Group