User
laktory.models.resources.databricks.User
¤
Bases: UserBase
Databricks user
Examples:
import io
from laktory import models
user_yaml = '''
user_name: john.doe@okube.ai
display_name: John Doe
group_ids:
- ${resources.group-role-engineer.id}
- ${resources.group-domain-finance.id}
roles:
- account_admin
'''
user = models.resources.databricks.User.model_validate_yaml(io.StringIO(user_yaml))
References
| BASE | DESCRIPTION |
|---|---|
acl_principal_id
|
identifier for use in databricks_access_control_rule_set, e.g.
TYPE:
|
active
|
Either user is active or not. True by default, but can be set to false in case of user deactivation with preserving user assets
TYPE:
|
allow_cluster_create
|
Allow the user to have cluster create privileges. Defaults to false. More fine grained permissions could be assigned with databricks_permissions and
TYPE:
|
allow_instance_pool_create
|
Allow the user to have instance pool create privileges. Defaults to false. More fine grained permissions could be assigned with databricks_permissions and instance_pool_id argument
TYPE:
|
api
|
Specifies whether to use account-level or workspace-level API. Valid values are
TYPE:
|
databricks_sql_access
|
This is a field to allow the user to have access to Databricks SQL UI, Databricks One and through databricks_sql_endpoint
TYPE:
|
disable_as_user_deletion
|
Deactivate the user when deleting the resource, rather than deleting the user entirely. Defaults to
TYPE:
|
display_name
|
This is an alias for the username that can be the full name of the user
TYPE:
|
external_id
|
ID of the user in an external identity provider
TYPE:
|
force
|
Ignore
TYPE:
|
force_delete_home_dir
|
This flag determines whether the user's home directory is deleted when the user is deleted. It will have not impact when in the accounts SCIM API. False by default
TYPE:
|
force_delete_repos
|
This flag determines whether the user's repo directory is deleted when the user is deleted. It will have no impact when in the accounts SCIM API. False by default
TYPE:
|
home
|
Home folder of the user, e.g.
TYPE:
|
repos
|
Personal Repos location of the user, e.g.
TYPE:
|
user_name
|
This is the username of the given user and will be their form of access and identity. Provided username will be converted to lower case if it contains upper case characters
TYPE:
|
workspace_access
|
This is a field to allow the user to have access to a Databricks Workspace UI and Databricks One
TYPE:
|
workspace_consume
|
This is a field to allow the user to have access only to Databricks One. Couldn't be used with
TYPE:
|
| LAKTORY | DESCRIPTION |
|---|---|
group_ids
|
List of the group ids that the user should be member of.
TYPE:
|
roles
|
List of roles assigned to the user e.g. ('account_admin')
TYPE:
|
workspace_permission_assignments
|
TYPE:
|
| ATTRIBUTE | DESCRIPTION |
|---|---|
additional_core_resources |
TYPE:
|
additional_core_resources
property
¤
- user roles
- user group members
laktory.models.resources.databricks.user.UserLookup
¤
Bases: ResourceLookup
| PARAMETER | DESCRIPTION |
|---|---|
user_id
|
ID of the user
TYPE:
|
user_name
|
User name of the user. The user must exist before this resource can be planned. Argument only supported by Terraform IaC backend.
TYPE:
|