Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix link in the TF provider doc #1923

Merged
merged 3 commits into from
Jan 16, 2023
Merged

Fix link in the TF provider doc #1923

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3c54f97
Fix link in the TF provider doc
grayluck Jan 12, 2023
6fe537a
Merge branch 'master' into patch-1
grayluck Jan 13, 2023
8d5fb16
Merge branch 'master' into patch-1
nfx Jan 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guides/gcp-workspace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ resource "databricks_mws_networks" "this" {

## Creating a Databricks Workspace

Once [the VPC](#Creating a VPC) is set up, you can create Databricks workspace through [databricks_mws_workspaces](../resources/mws_workspaces.md) resource.
Once [the VPC](#creating-a-vpc) is set up, you can create Databricks workspace through [databricks_mws_workspaces](../resources/mws_workspaces.md) resource.

Code that creates workspaces and code that [manages workspaces](workspace-management.md) must be in separate terraform modules to avoid common confusion between `provider = databricks.accounts` and `provider = databricks.created_workspace`. This is why we specify `databricks_host` and `databricks_token` outputs, which have to be used in the latter modules.

Expand Down