Describe the issue
Executing databricks storage-credential get --debug brings up the list of storage credentials, but fails after selection with 404 on Azure Databricks.
...
< "id": "cfc0ee29-e58e-4519-9895-9be37ca215a5",
...
12:54:00 DEBUG non-retriable error: Storage Credential 'cfc0ee29-e58e-4519-9895-9be37ca215a5' does not exist. pid=2421110 sdk=true
12:54:00 DEBUG GET /api/2.1/unity-catalog/storage-credentials/cfc0ee29-e58e-4519-9895-9be37ca215a5
Within WebUIs ajax-api the .name is used instead of the .id.
GET https://<workspace-id>.azuredatabricks.net/ajax-api/2.1/unity-catalog/storage-credentials/identityName
Status 200
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
- Run
databricks storage-credential get --debug on a databricks azure workspace that has storage-credentials defined
Expected Behavior
The command should return the entity after selection.
Actual Behavior
The command errors.
OS and CLI version
Databricks CLI v0.210.2
Linux
Describe the issue
Executing
databricks storage-credential get --debugbrings up the list of storage credentials, but fails after selection with 404 on Azure Databricks.Within WebUIs
ajax-apithe.nameis used instead of the.id.Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
databricks storage-credential get --debugon a databricks azure workspace that has storage-credentials definedExpected Behavior
The command should return the entity after selection.
Actual Behavior
The command errors.
OS and CLI version
Databricks CLI v0.210.2
Linux