kebandClaude Opus 5.5
09bacd8438
- `l` goes to the details of what is selected; `enter` still drills in - vaults, scopes and files show their details (vault settings from the listing, no extra requests) - with nothing to show, the right pane says how to get started - a list from the cache says how old it is while it reloads - what is expiring, in the status pane and `lazysecrets expiring` - when access is refused, what to check, for Azure and Databricks - no group list in an account's details, and no Microsoft Graph call for it Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# Databricks
|
|
|
|
Workspaces come from the profiles in `~/.databrickscfg` (or
|
|
`$DATABRICKS_CONFIG_FILE`); account-console profiles are skipped. Each
|
|
workspace is a source, its secret scopes are the vaults.
|
|
|
|
Credentials are resolved the same way as the Databricks CLI, so
|
|
`auth_type = azure-cli` uses your az login and OAuth profiles use
|
|
`databricks auth login`. When a login expires, `L` runs the right one for
|
|
that profile.
|
|
|
|
Secrets in Azure Key Vault-backed scopes are read through Databricks; if
|
|
Databricks refuses, lazysecrets reads the backing vault directly with your
|
|
az login (which then needs the [Key Vault roles](azure.md#permissions)).
|
|
|
|
When Databricks refuses, the pane says what to check: access to the
|
|
workspace and READ on the scope, or, when the workspace's IP access list
|
|
refused, the network you're on.
|
|
|
|
On a scope, the right pane shows who has access to it and how much
|
|
(manage, write, read). Databricks shows that only to the scope's
|
|
managers; to others it says so.
|
|
|
|
Hide profiles you don't want in the [config](config.md):
|
|
|
|
```yaml
|
|
providers:
|
|
databricks:
|
|
hideProfiles: [test]
|
|
```
|