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
Clarify optionality of databricks_mws_workspaces.deployment_name in docs and examples (#1315)
* Drop deployment_name from aws-workspaces worked example
* Reflect optionality in references to deployment_name
* Apply suggestions from code review
Co-authored-by: Serge Smertin <[email protected]>
@@ -206,7 +204,7 @@ The following arguments are available and cannot be changed after workspace is c
206
204
207
205
*`account_id` - Account Id that could be found in the bottom left corner of [Accounts Console](https://accounts.cloud.databricks.com/).
208
206
*`managed_services_customer_managed_key_id` - (Optional) `customer_managed_key_id` from [customer managed keys](mws_customer_managed_keys.md) with `use_cases` set to `MANAGED_SERVICES`. This is used to encrypt the workspace's notebook and secret data in the control plane.
209
-
*`deployment_name` - (Optional) part of URL: `https://<deployment-name>.cloud.databricks.com`
207
+
*`deployment_name` - (Optional) part of URL as in `https://<prefix>-<deployment-name>.cloud.databricks.com`. Deployment name cannot be used until a deployment name prefix is defined. Please contact your Databricks representative. Once a new deployment prefix is added/updated, it only will affect the new workspaces created.
210
208
*`workspace_name` - name of the workspace, will appear on UI
211
209
*`aws_region` - AWS region of VPC
212
210
*`storage_configuration_id` - `storage_configuration_id` from [storage configuration](mws_storage_configurations.md)
0 commit comments