In the documentation from Databricks it says to run the below for binding a storage credential to a workspace (after already completing step 1 to update the `isolation-mode` to be `ISOLATED`): 

databricks workspace-bindings update-bindings storage-credential <my-storage-credential> \
--json '{
  "add": [{"workspace_id": <workspace-id>}...],
  "remove": [{"workspace_id": <workspace-id>}...]
}' --profile <profile-name>

However, when running this (with my <storage-credential>, <workspace-id>, and <profile-name>) I receive an error: 

Error: Supported binding types for STORAGE_CREDENTIAL are BINDING_TYPE_READ_WRITE

It explicitly states in the documentation that you don't even need to specify a `binding_type` in the json as the read-only binding is not available for storage credentials. But I receive this error which seems as if I have set an incorrect binding type, even though I have not set one at all. I am confident in the rest of the syntax and authentication, because if I add the workspace binding manually in the Databricks UI I can run this same command to "remove" the binding and it runs successfully.

If I do include the `binding_type` of `BINDING_TYPE_READ_WRITE` in the json, I receive an error 

Error: assigned workspace 0 does not exist or is not assigned the same metastore as the current workspace.

Is the documentation incorrect, or is there a bug in workspace binding for storage-credentials via the CLI?