You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to be able to determine the owner of workspace paths, such as notebooks. This is needed to associate a user with a resource, such as a notebook or python script.
Proposed Solution
It's unclear how to use the SDK to determine the owner of a path that matches what the UI shows. However we should be able to use the permissions APIs to determine a user that has CAN_MANAGE on the path. If nothing better can be found, that user can be considered the owner.
Additional Context
In PR #2761 we introduced a framework for determining the owners of objects. However the initial implementation does not determine a direct owner for workspace paths, meaning the fallback of a workspace or account administrator is used instead.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem statement
We need to be able to determine the owner of workspace paths, such as notebooks. This is needed to associate a user with a resource, such as a notebook or python script.
Proposed Solution
It's unclear how to use the SDK to determine the owner of a path that matches what the UI shows. However we should be able to use the permissions APIs to determine a user that has
CAN_MANAGE
on the path. If nothing better can be found, that user can be considered the owner.Additional Context
In PR #2761 we introduced a framework for determining the owners of objects. However the initial implementation does not determine a direct owner for workspace paths, meaning the fallback of a workspace or account administrator is used instead.
The text was updated successfully, but these errors were encountered: