subcategory |
---|
Security |
This resource allows you to manage groups in Databricks Workspace or Account Console (for AWS deployments). You can also associate Databricks users to groups. This is useful if you are using an application to sync users & groups with SCIM API.
Recommended to use along with Identity Provider SCIM provisioning to populate users into those groups:
Creating some group
resource "databricks_group" "this" {
display_name = "Some Group"
allow_cluster_create = true
allow_instance_pool_create = true
}
Adding databricks_user as databricks_group_member of some group
resource "databricks_group" "this" {
display_name = "Some Group"
allow_cluster_create = true
allow_instance_pool_create = true
}
resource "databricks_user" "this" {
user_name = "[email protected]"
}
resource "databricks_group_member" "vip_member" {
group_id = databricks_group.this.id
member_id = databricks_user.this.id
}
The following arguments are supported:
display_name
- (Required) This is the display name for the given group.external_id
- (Optional) ID of the group in an external identity provider.allow_cluster_create
- (Optional) This is a field to allow the group to have cluster create privileges. More fine grained permissions could be assigned with databricks_permissions and cluster_id argument. Everyone withoutallow_cluster_create
argument set, but with permission to use Cluster Policy would be able to create clusters, but within boundaries of that specific policy.allow_instance_pool_create
- (Optional) This is a field to allow the group to have instance pool create privileges. More fine grained permissions could be assigned with databricks_permissions and instance_pool_id argument.databricks_sql_access
- (Optional) This is a field to allow the group to have access to Databricks SQL feature in User Interface and through databricks_sql_endpoint.workspace_access
- (Optional) This is a field to allow the group to have access to Databricks Workspace.force
- (Optional) Ignorecannot create group: Group with name X already exists.
errors and implicitly import the specific group into Terraform state, enforcing entitlements defined in the instance of resource. This functionality is experimental and is designed to simplify corner cases, like Azure Active Directory synchronisation.
In addition to all arguments above, the following attributes are exported:
id
- The id for the group object.
You can import a databricks_group
resource with the name my_group
like the following:
$ terraform import databricks_group.my_group <group_id>