=========================
In this template, we show how to deploy a workspace with managed VPC.
- You need to have run gcp-sa-provisionning and have a service account to fill in the variables.
- If you want to deploy to a new project, you will need to grant the custom role generated in that template to the service acount in the new project.
- The Service Account needs to be added as Databricks Admin in the account console
You can do the same thing by provisionning a service account that will have the same permissions - and associate the key associated to it.
- You need to fill in the
variables.tf - run
terraform init - run
teraform apply
No requirements.
No providers.
| Name | Source | Version |
|---|---|---|
| gcp-basic | github.com/databricks/terraform-databricks-examples/modules/gcp-workspace-basic | n/a |
No resources.
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| databricks_account_id | Databricks Account ID | string |
n/a | yes |
| databricks_google_service_account | Email of the service account used for deployment | string |
n/a | yes |
| delegate_from | Identities to allow to impersonate created service account (in form of user:user.name@example.com, group:deployers@example.com or serviceAccount:sa1@project.iam.gserviceaccount.com) | list(string) |
n/a | yes |
| google_project | Google project for VCP/workspace deployment | string |
n/a | yes |
| google_region | Google region for VCP/workspace deployment | string |
n/a | yes |
| google_zone | Zone in GCP region | string |
n/a | yes |
| prefix | Prefix to use in generated VPC name | string |
n/a | yes |
| workspace_name | Name of the workspace to create | string |
n/a | yes |
| Name | Description |
|---|---|
| databricks_host | n/a |
| databricks_token | n/a |