Turns out the problem was that azureblob doesn't honor
CredentialSupplier like aws-s3.
Argh - glad you were able to figure it out!
ap
Turns out the problem was that azureblob doesn’t honor CredentialSupplier
like aws-s3. We changed to using CredentialSupplier instead of passing a
Credential and the username and password never make it into the context.
Easy to fix - hard to find.
Thanks for the quick response.
John
On Tue, Jul
but still digging through that.
Looks like ExpandProperties is where this happens:
https://github.com/apache/jclouds/blob/master/core/src/main/java/org/jclouds/functions/ExpandProperties.java
Given that this hasn't changed and probably isn't broken given how
widely it's used, my first questio
Does anyone know which library is responsible for this?
Judging by testVariablesReplaceOnEndpoint() in ContextBuilderTest [1], I
suspect jclouds is doing this itself. I'm assuming it's somewhere in
ContextBuilder [2] but still digging through that.
Hope that helps!
ap
[1]
https://github.c
Hi all,
We updated some libraries in our pom the other day and suddenly we talk to
azure blob. Turns out the endpoint for azure in the azureblob has an
interpolated variable for the host - like this:
public static class Builder extends BaseProviderMetadata.Builder {
protected Builder() {
