Azure Blob Storage S3 compatibility not working - incorrect URL path style

[humi-jderycke]

When using Azure Blob Storage as the S3-compatible storage backend, Probo fails to upload files due to incorrect URL construction by the AWS SDK v2.
https://www.getprobo.com/docs/self-hosting/kubernetes#azure-deployment

Current Behavior:
https://probo.mystorageaccount.blob.core.windows.net/...

Expected behavior:
https://mystorageaccount.blob.core.windows.net/probo/...

Error Message:
cannot import framework: cannot upload logo file: cannot upload file to S3: operation error S3: PutObject, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Put "https://probo.mystorageaccount.blob.core.windows.net...?x-id=PutObject": dial tcp: lookup probo.mystorageaccount.blob.core.windows.net on 10.0.0.10:53: no such host

Expected Behavior:
Probo should successfully upload files to Azure Blob Storage containers.

[gearnode]

#610

[SachaProbo]

We have merged a fix for your issue: d6abaec

You need to add --set s3.usePathStyle=true

Can you tell us if you still have any issues?

[humi-jderycke]

Hi, thanks for the quick support!
There still seems to be an issue, I now have the following environment variables in my pod, running image v0.111.0
AWS_USE_PATH_STYLE=true
AWS_ENDPOINT=https://account.blob.core.windows.net
AWS_REGION=us-east-1
AWS_SECRET_ACCESS_KEY=
AWS_ACCESS_KEY_ID=account
AWS_BUCKET=probo

But when I try to add a framework it doesn't use the path style:
"error":"cannot import framework: cannot uploa d logo file: cannot upload file to S3: operation error S3: PutObject, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Put "https://probo.account.blob.core.windows.net/019b31b9-0045-7000-8939-7afe69a70fdf?x-id=PutObject\": dial tcp: lookup probo.account.blob.core.windows.net on 10.0.0.10:53: no such host"

[SachaProbo]

Sorry for the delay. We are not familiar with Azure, so we actually made a mistake: Azure Blob Storage is not fully compatible with S3, and we need to make a few changes to make our application compatible with both storage systems. For now, we will update the documentation and implement this feature later.