You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the abfs block to create a mount in Azure Government, the mount fails with the following error: Error: cannot create mount: Mount failed due to invalid mount source [abfss..//<container_name>@<sa_name>.dfs.core.windows.net].
This error is thrown because the URI is incorrect for storage accounts in Azure Government. Instead, the URI should end with core.usgovcloudapi.net. See here for the source of the problem.
Steps to Reproduce
Create a storage account/container in Azure Government
Use the abfs block in a databricks_mount resource to mount the container to a Databricks workspace
This should only be a problem on Azure Government, potentially other Azure Clouds that do not use the standard dfs.core.windows.net zone for storage accounts.
Would you like to implement a fix?
Not immediately.
Workaround
You can workaround this issue by using a combination of the uri and extra_configs parameters like the example below.
You can reproduce this JSON with the Azure CLI: az cloud list | jq '.[] | {name, cloudEndpoint: .endpoints.resourceManager, storageEndpoint: .suffixes.storageEndpoint}'.
Configuration
Expected Behavior
The mount should be created as expected.
Actual Behavior
When using the
abfs
block to create a mount in Azure Government, the mount fails with the following error:Error: cannot create mount: Mount failed due to invalid mount source [abfss..//<container_name>@<sa_name>.dfs.core.windows.net]
.This error is thrown because the URI is incorrect for storage accounts in Azure Government. Instead, the URI should end with
core.usgovcloudapi.net
. See here for the source of the problem.Steps to Reproduce
abfs
block in adatabricks_mount
resource to mount the container to a Databricks workspaceTerraform and provider versions
Is it a regression?
No
Important Factoids
dfs.core.windows.net
zone for storage accounts.Would you like to implement a fix?
Not immediately.
Workaround
You can workaround this issue by using a combination of the
uri
andextra_configs
parameters like the example below.This will make the provider use the correct URI.
The text was updated successfully, but these errors were encountered: