Error binding storage credential & external location to workspace

Open
#3,945 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start by reproducing the issue with the databricks workspace-bindings update-bindings storage-credential command and the JSON payload shown, using Databricks CLI v0.276.0. Compare the storage credential and external location binding paths and their accepted binding types; done means both can be added to the workspace without the reported error.

Written by the indexing model from the issue text.

Description

CLI
Describe the issue

Error binding both storage credential or external location to a workspace via CLI when running code in Step 1 below. See error below. Databricks documentation states Read-only binding (BINDING_TYPE_READ_ONLY) is not available for storage credentials. Therefore there is no reason to set binding_type for the storage credentials binding. However I receive the error below, which seems as if I have set an incorrect binding type, even though I have not set one at all in the json. Note that this command does work to remove a binding that you have added manually within the Databricks UI.
Additionally, if I do provide a binding_type I receive a different error.

Steps to reproduce the behavior
  1. Run databricks workspace-bindings update-bindings storage-credential <my-storage-credential> \ --json '{ "add": [{"workspace_id": <workspace-id>}] }' --profile <profile-name>
  2. See error
Expected Behavior

Successfully bind the storage credential or external location to <workspace-id>

Actual Behavior

Received error Error: Supported binding types for STORAGE_CREDENTIAL are BINDING_TYPE_READ_WRITE

OS and CLI version

Windows, Databricks CLI v0.276.0

Is this a regression?

No, has not worked for previous versions that I have seen.

Dominant language
Go
Stars
427
Forks
267
Avg merge
2d 1h
Merged PRs (30d)
233

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/cli

All issues in databricks/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.