Invalidate cached RequestAdapter of KiotaRequestAdapterHook if session of AuthenticationProvider is closed#69128
Merged
Merged
Conversation
boring-cyborg
Bot
added
area:providers
provider:microsoft-azure
dabla
changed the title
dabla
force-pushed
the
fix/msgraph-session-closed
branch
3 times, most recently
from
a696020 to
6a12ee7
Compare
SameerMesiah97
left a comment
SameerMesiah97
left a comment
Contributor
There was a problem hiding this comment.
Needs one clarification. I have left a few comments.
…uestAdapter isn't closed for KiotaRequestAdapterHook, if so invalidate the cached RequestAdapter
dabla
force-pushed
the
fix/msgraph-session-closed
branch
from
6a12ee7 to
8005600
Compare
eladkal
approved these changes
Jul 2, 2026
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
3 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.
Check if session of credentials provider in cached RequestAdapter of KiotaRequestAdapterHook isn't closed, if so invalidate the cached RequestAdapter.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.