-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Update table names for databricks_workspace_workspace
and databricks_catalog_catalog
#4
Changes from 3 commits
4457d11
67f8251
d9ee44c
7b950c3
9dc4e20
0d1ad27
15bb748
03b2e41
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -114,27 +114,27 @@ connection "databricks" { | |
} | ||
``` | ||
|
||
By default, all options are commented out in the default connection, thus Steampipe will resolve your credentials using the same mechanism as the Databricks CLI (Databricks environment variables, default profile, etc). This provides a quick way to get started with Steampipe, but you will probably want to customize your experience using configuration options for [querying multiple regions](#multi-account-connections), [configuring credentials](#configuring-databricks-credentials) from your [Databricks Profiles](#databricks-profile-credentials). | ||
You can customize your experience using configuration options for [querying multiple accounts](#multi-account-connections), [configuring credentials](#configuring-databricks-credentials) from your [Databricks Profiles](#databricks-profile-credentials). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we can add support to the plugin to pickup the |
||
|
||
## Multi-Account Connections | ||
|
||
You may create multiple databricks connections: | ||
```hcl | ||
connection "databricks_dev" { | ||
plugin = "databricks" | ||
profile = "databricks_dev" | ||
config_profile = "databricks_dev" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can this config arg just be called There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reference points for naming: For env vars:
From Terraform (https://registry.terraform.io/providers/databricks/databricks/latest/docs#argument-reference):
In their Config struct (https://github.com/databricks/databricks-sdk-go/blob/main/config/config.go#L54-L60):
|
||
account_id = abcdd0f81-9be0-4425-9e29-3a7d96782373 | ||
} | ||
|
||
connection "databricks_qa" { | ||
plugin = "databricks" | ||
profile = "databricks_qa" | ||
config_profile = "databricks_qa" | ||
account_id = wxyzd0f81-9be0-4425-9e29-3a7d96782373 | ||
} | ||
|
||
connection "databricks_prod" { | ||
plugin = "databricks" | ||
profile = "databricks_prod" | ||
config_profile = "databricks_prod" | ||
account_id = pqrsd0f81-9be0-4425-9e29-3a7d96782373 | ||
} | ||
``` | ||
|
@@ -206,19 +206,19 @@ account_id = abcdd0f81-9be0-4425-9e29-3a7d96782373 | |
```hcl | ||
connection "databricks_user1-account" { | ||
plugin = "databricks" | ||
profile = "user1-account" | ||
config_profile = "user1-account" | ||
account_id = "abcdd0f81-9be0-4425-9e29-3a7d96782373" | ||
} | ||
|
||
connection "databricks_user1-workspace" { | ||
plugin = "databricks" | ||
profile = "user1-workspace" | ||
config_profile = "user1-workspace" | ||
account_id = "abcdd0f81-9be0-4425-9e29-3a7d96782373" | ||
} | ||
|
||
connection "databricks_user1-basic" { | ||
plugin = "databricks" | ||
profile = "user1-basic" | ||
config_profile = "user1-basic" | ||
account_id = "abcdd0f81-9be0-4425-9e29-3a7d96782373" | ||
} | ||
``` | ||
|
@@ -241,7 +241,7 @@ account_id = abcdd0f81-9be0-4425-9e29-3a7d96782373 | |
```hcl | ||
connection "databricks_user1-account" { | ||
plugin = "databricks" | ||
profile = "user1-account" | ||
config_profile = "user1-account" | ||
account_id = "abcdd0f81-9be0-4425-9e29-3a7d96782373" | ||
} | ||
``` | ||
|
@@ -264,7 +264,7 @@ account_id = abcdd0f81-9be0-4425-9e29-3a7d96782373 | |
```hcl | ||
connection "databricks_user1-workspace" { | ||
plugin = "databricks" | ||
profile = "user1-workspace" | ||
config_profile = "user1-workspace" | ||
account_id = "abcdd0f81-9be0-4425-9e29-3a7d96782373" | ||
} | ||
``` | ||
|
@@ -291,7 +291,7 @@ connection "databricks_user1-workspace" { | |
|
||
### Credentials from Environment Variables | ||
|
||
Alternatively, you can also use the standard Databricks environment variables to obtain credentials **only if other argument (`profile`, `account_id`, `account_token`/`account_host`/`workspace_token`/`workspace_host`) is not specified** in the connection: | ||
Alternatively, you can also use the standard Databricks environment variables to obtain credentials **only if other argument (`config_profile`, `account_id`, `account_token`/`account_host`/`workspace_token`/`workspace_host`) is not specified** in the connection: | ||
|
||
```sh | ||
export DATABRICKS_CONFIG_PROFILE=user1-test | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though it's making an exception to the rule of following the SDK directory naming for services (the most consistent source we could find), we could treat
job
andpipeline
as the service names instead ofjobs
andpipelines
respectively. This would mean we'd have the table names:databricks_job
databricks_job_run
databricks_pipeline
databricks_pipeline_event
databricks_pipeline_update
These seem like better table names than what we originally have