Bug: workspace export with direct-download still tries to interpret the response as JSON

[gerashegalov]

Export a file with # such as an init script in bash

databricks workspace export '/Users/user@email/init.sh' --direct-download
Error: invalid character '#'

workaround:

databricks workspace export '/Users/user@email/init.sh' | jq -r .content | base64 -d

[pietern]

Thanks for reporting this issue. The direct download option has been removed from the SDK in a newer release because it's the only API that switches the response content type depending on the request payload. To make it easier to use I added a change that automatically decodes the base64 payload and prints it to stdout, so you don't need to use the workaround.