fix azureblob endpoint typo

[felix-sift]

No description provided.

[felix-sift]

@CRThaze poke

[felix-sift]

@CRThaze poke

[felix-sift]

@andrescrz poke

[CRThaze]

@felix-sift can you please share more details about your image versions and override values you're testing with? We have not had an issue with this, and the purpose is to allow for multiple backends from conflicting with each other.

[felix-sift]

@felix-sift can you please share more details about your image versions and override values you're testing with? We have not had an issue with this, and the purpose is to allow for multiple backends from conflicting with each other.

for sure, i'm using v3.2 of s3proxy.

here's my config:

s3proxy.identity=local-identity
s3proxy.credential=local-credential
jclouds.credential=
s3proxy.endpoint=http://0.0.0.0:9000
s3proxy.authorization=none
jclouds.provider=azureblob-sdk
jclouds.endpoint=https://blahblahgh.blob.core.usgovcloudapi.net
jclouds.identity=

if jcloud.identity or jclouds.credential is unset, the app errors that both of these vars must be set.

if jcloud.azureblob.endpoint is set, the below error occurs.

reactor.netty.channel.ChannelOperationsHandler)}
[s3proxy] E 07-08 23:57:15.618 S3Proxy-Jetty-32 c.a.c.h.n.NettyAsyncHttpClient:531 |::] java.net.UnknownHostException: .blob.core.windows.net: Name or service not known
java.io.UncheckedIOException: java.net.UnknownHostException: .blob.core.windows.net: Name or service not known
	at com.azure.core.http.netty.NettyAsyncHttpClient.sendSync(NettyAsyncHttpClient.java:200)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:51)
	at com.azure.storage.common.policy.ScrubEtagPolicy.processSync(ScrubEtagPolicy.java:35)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:53)
	at com.azure.core.http.policy.HttpLoggingPolicy.processSync(HttpLoggingPolicy.java:175)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:53)
	at com.azure.storage.common.policy.ResponseValidationPolicyBuilder$ResponseValidationPolicy.processSync(ResponseValidationPolicyBuilder.java:140)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:53)
	at com.azure.core.implementation.http.policy.InstrumentationPolicy.processSync(InstrumentationPolicy.java:101)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:53)
	at com.azure.core.http.policy.BearerTokenAuthenticationPolicy.processSync(BearerTokenAuthenticationPolicy.java:175)
	at com.azure.core.http.HttpPipelineNextSyncPolicy.processSync(HttpPipelineNextSyncPolicy.java:53)
	at com.azure.stor

[felix-sift]

we are using workload identity, so we don't have any azure credentials set.

[CRThaze]

Thanks for the details. We will take a look. We have not tested with s3proxy 3.x.x yet, but are planning to do so shortly. As I said before the azureblob portion was there to allow for working with multiple backends, we will check what needs doing for v3.