Updated value of anon to be False#540
Conversation
kyleknap
left a comment
There was a problem hiding this comment.
Looks good! I just had some smaller feedback.
nateprewitt
left a comment
There was a problem hiding this comment.
A few thoughts/nits but this looks good overall! I think it's important we make it clearer how to get back to the old behavior since users may not be invoking adlfs directly.
ec9a4c7 to
85f2ba8
Compare
kyleknap
left a comment
There was a problem hiding this comment.
This is looking good. I just had some smaller follow up comments/suggestions.
|
For the edge case of adding the SAS token to the account host, I tried it and it gives a ClientAuthenticationError, so I don't think it will be an issue. |
|
@anjaliratnam-msft I tried adding the SAS token as a query string to Looking more into this, while it seems possible that SAS token could be provided to the If setting |
kyleknap
left a comment
There was a problem hiding this comment.
Looks good to me! Thanks for all of the hard work here! 🚢
We are updating the default value of
anonto beFalsewhich means that anonymous authentication will not be used unlessanon=Trueis explicitly passed in when instantiatingAzureBlobFileSystem.DefaultAzureCredentialswill now become the default authentication method. This resolves #348.