Add fsspec authentication environment variables to deltares example notebook. - #301
Merged
Merged
Conversation
Marc Lichtman (777arc)
self-requested a review
December 5, 2024 16:57
Marc Lichtman (777arc)
approved these changes
Dec 5, 2024
Christopher Polster (chpolste)
added a commit
to CLIMAAX/FLOODS
that referenced
this pull request
Dec 6, 2024
Following the changes in microsoft/PlanetaryComputerExamples#301. The adlfs package is now required for data access and has been added to the environment.
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.
If fsspec sees a URI that starts with https:// (that was previously in the asset href of the deltares STAC items) then fsspec assumes that URI is publicly accessible and doesn’t try to use any of the authentication kwargs you pass to xarray. fsspec will only use the authentication arguments if the URI has a protocol for an fsspec backend, abfs:// in our case.
But we need to set the environment variables because there is 2 layers of requests happening, the first for the index file (xarray will forwards kwargs correctly for that one) and the second for the chunk ranges (xarray will not forward kwargs correctly for that one, or at least I couldn’t figure it out). The environment variables allow us to “remotely” tell fsspec what credentials to unconditionally use for all requests.