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
* Optional Resource Group creation in adb-lakehouse module
The commit contains the implementation for the workspace resource group. However this change requires to no more use the local.rg_location variable, since the value is known after the apply, and rhis force the replacement of all of the resources
* Fix resource group name value in the azure data factory resource
* Document examples
Most of README files were already defined. TFDocs updated in each of them
* Remove modules reference and change how to use guide
Copy file name to clipboardExpand all lines: examples/aws-workspace-config/README.md
+11-21
Original file line number
Diff line number
Diff line change
@@ -69,49 +69,39 @@ The process will be: provision ordinary users -> assign users to groups -> assig
69
69
70
70
You can manage users/groups inside terraform. Examples were given in `main.tf`. Note that with Unity Catalog, you can have account level users/groups. The example here is at workspace level.
|[databricks_spark_version.latest_lts](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/spark_version)| data source |
101
-
|[databricks_user.this](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/user)| data source |
92
+
|[databricks_user.this](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/user)| data source |
102
93
103
94
## Inputs
104
95
105
96
| Name | Description | Type | Default | Required |
Copy file name to clipboardExpand all lines: examples/aws-workspace-uc-simple/README.md
+67
Original file line number
Diff line number
Diff line change
@@ -14,3 +14,70 @@ When running tf configs for UC resources, due to sometimes requires a few minute
14
14
> Step 1: Fill in values in `terraform.tfvars`; also configure env necessary variables for AWS provider authentication.
15
15
16
16
> Step 2: Run `terraform init` and `terraform apply` to deploy the resources. This will deploy both AWS resources that Unity Catalog requires and Databricks Account Level resources.
|[aws_caller_identity.current](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/caller_identity)| data source |
56
+
|[databricks_node_type.smallest](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/node_type)| data source |
57
+
|[databricks_service_principal.admin_service_principal](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/service_principal)| data source |
58
+
|[databricks_spark_version.latest_version](https://registry.terraform.io/providers/databricks/databricks/latest/docs/data-sources/spark_version)| data source |
59
+
60
+
## Inputs
61
+
62
+
| Name | Description | Type | Default | Required |
| <aname="input_aws_access_services_role_name"></a> [aws\_access\_services\_role\_name](#input\_aws\_access\_services\_role\_name)| (Optional) Name for the AWS Services role by this module |`string`|`null`| no |
65
+
| <aname="input_aws_profile"></a> [aws\_profile](#input\_aws\_profile)| (Required) AWS cli profile to be used for authentication with AWS |`string`| n/a | yes |
66
+
| <aname="input_cidr_block"></a> [cidr\_block](#input\_cidr\_block)| (Required) CIDR block to be used to create the Databricks VPC |`string`| n/a | yes |
| <aname="input_databricks_client_id"></a> [databricks\_client\_id](#input\_databricks\_client\_id)| (Required) Client ID to authenticate the Databricks provider at the account level |`string`| n/a | yes |
69
+
| <aname="input_databricks_client_secret"></a> [databricks\_client\_secret](#input\_databricks\_client\_secret)| (Required) Client secret to authenticate the Databricks provider at the account level |`string`| n/a | yes |
70
+
| <aname="input_databricks_metastore_admins"></a> [databricks\_metastore\_admins](#input\_databricks\_metastore\_admins)| List of Admins to be added at account-level for Unity Catalog.<br/> Enter with square brackets and double quotes<br/> e.g ["[email protected]", "[email protected]"]|`list(string)`| n/a | yes |
71
+
| <aname="input_databricks_users"></a> [databricks\_users](#input\_databricks\_users)| List of Databricks users to be added at account-level for Unity Catalog.<br/> Enter with square brackets and double quotes<br/> e.g ["[email protected]", "[email protected]"]|`list(string)`| n/a | yes |
72
+
| <aname="input_my_username"></a> [my\_username](#input\_my\_username)| (Required) Username in the form of an email to be added to the tags and be declared as owner of the assets |`string`| n/a | yes |
73
+
| <aname="input_region"></a> [region](#input\_region)| (Required) AWS region where the assets will be deployed |`string`| n/a | yes |
74
+
| <aname="input_tags"></a> [tags](#input\_tags)| (Optional) List of tags to be propagated accross all assets in this demo |`map(string)`| n/a | yes |
75
+
| <aname="input_unity_admin_group"></a> [unity\_admin\_group](#input\_unity\_admin\_group)| (Required) Name of the admin group. This group will be set as the owner of the Unity Catalog metastore |`string`| n/a | yes |
76
+
| <aname="input_workspace_name"></a> [workspace\_name](#input\_workspace\_name)| (Required) Databricks workspace name to be used for deployment |`string`| n/a | yes |
0 commit comments