feat: add support for other Azure credentials#3482
Merged
snowman2 merged 5 commits intorasterio:mainfrom Dec 27, 2025
Merged
Conversation
jessjaco
changed the title
snowman2
reviewed
Dec 15, 2025
Member
|
@jessjaco I am planning on making a final release candidate on 12/29. If you would like this change in 1.5 this will need to be merged before then. |
Contributor
Author
|
Ok, I altered the changes to make the logic clearer. I also removed the class variables, since they are available in the credentials object. |
snowman2
reviewed
Dec 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a solution for #3423, adding support for all env var based authentication methods for reading data for Azure blob storage, as described here. The logic mimics that defined in the corresponding gdal code.
The solution ended up more verbose than anticipated to maintain existing logic. Specifically, if keyword arguments are passed to
AzureSession, they always take precedent over existing environmental variables.