ServicePrincipal
laktory.models.resources.databricks.ServicePrincipal
¤
Bases: ServicePrincipalBase
Databricks account service principal
Examples:
import io
from laktory import models
sp_yaml = '''
display_name: neptune
application_id: baf147d1-a856-4de0-a570-8a56dbd7e234
group_ids:
- ${resources.group-role-engineer.id}
- ${resources.group-domain-finance.id}
roles:
- account_admin
'''
sp = models.resources.databricks.ServicePrincipal.model_validate_yaml(
io.StringIO(sp_yaml)
)
References
| BASE | DESCRIPTION |
|---|---|
acl_principal_id
|
identifier for use in databricks_access_control_rule_set, e.g.
TYPE:
|
active
|
Either service principal is active or not. True by default, but can be set to false in case of service principal deactivation with preserving service principal assets
TYPE:
|
allow_cluster_create
|
Allow the service principal 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 service principal 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:
|
application_id
|
TYPE:
|
databricks_sql_access
|
This is a field to allow the service principal to have access to Databricks SQL feature through databricks_sql_endpoint
TYPE:
|
disable_as_user_deletion
|
Deactivate the service principal when deleting the resource, rather than deleting the service principal entirely. Defaults to
TYPE:
|
display_name
|
This is an alias for the service principal and can be the full name of the service principal
TYPE:
|
external_id
|
ID of the service principal in an external identity provider
TYPE:
|
force
|
Ignore
TYPE:
|
force_delete_home_dir
|
This flag determines whether the service principal's home directory is deleted when the user is deleted. It will have no impact when in the accounts SCIM API. False by default
TYPE:
|
force_delete_repos
|
This flag determines whether the service principal'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 service principal, e.g.
TYPE:
|
repos
|
Personal Repos location of the service principal, e.g.
TYPE:
|
workspace_access
|
This is a field to allow the service principal to have access to a Databricks Workspace
TYPE:
|
workspace_consume
|
This is a field to allow the service principal to have access to a Databricks Workspace as consumer, with limited access to workspace UI. 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
¤
- service principal roles
- service principal group members
laktory.models.resources.databricks.serviceprincipal.ServicePrincipalLookup
¤
Bases: ResourceLookup
| PARAMETER | DESCRIPTION |
|---|---|
application_id
|
ID of the service principal. The service principal must exist before this resource can be retrieved.
TYPE:
|