pyaz/synapse/role/assignment/__init__.py
def list(workspace_name, assignee=None, assignee_object_id=None, item=None, item_type=None, role=None, scope=None):
    '''
    List role assignments.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Assigning a role with workspace scope grants permissions to all applicable objects in the workspace.
    '''
    return _call_az("az synapse role assignment list", locals())

    List role assignments.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Assigning a role with workspace scope grants permissions to all applicable objects in the workspace.
    
List role assignments.
Required Parameters:
workspace_name -- The workspace name.

Optional Parameters:
assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
item -- Item granted access in the workspace.
List role assignments . Required Parameters : workspace_name -- The workspace name . Optional Parameters : assignee -- Represent a user or service principal . Supported format : object id user sign - in name or service principal name . assignee_object_id -- Use this parameter instead of ' -- assignee ' to bypass Graph API invocation in case of insufficient privileges . This parameter only works with object ids for users groups service principals and managed identities . For managed identities use the principal id . For service principals use the object id and not the app id . item -- Item granted access in the workspace .
def list(workspace_name, assignee=None, assignee_object_id=None, item=None, item_type=None, role=None, scope=None):
    return _call_az("az synapse role assignment list", locals())
def list ( workspace_name , assignee = None , assignee_object_id = None , item = None , item_type = None , role = None , scope = None ) : return _call_az ( "az synapse role assignment list" , locals ( ) )
List role assignments.
List role assignments .
'''
    List role assignments.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Assigning a role with workspace scope grants permissions to all applicable objects in the workspace.
    '''
workspace_name
assignee
assignee_object_id
item
item_type
role
scope