Skip to content

[Storage] Fix listener to use the target data blob client over the host #50431

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

amnguye
Copy link
Member

@amnguye amnguye commented Jun 4, 2025

Fixes #49993

@Copilot Copilot AI review requested due to automatic review settings June 4, 2025 20:59
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes an issue where the blob listener was incorrectly using the host blob client instead of the target data blob client.

Comments suppressed due to low confidence (1)

sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Blobs/src/Listeners/BlobListenerFactory.cs:110

  • Replacing primaryBlobClient with targetBlobClient ensures that the listener is monitoring the correct data blob client, which resolves the reported issue. Please verify that other related instances of the primaryBlobClient usage have been updated accordingly if they are related to this context.
await RegisterWithSharedBlobListenerAsync(hostId, sharedBlobListener, targetBlobClient,

@github-actions github-actions bot added the Storage Storage Service (Queues, Blobs, Files) label Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Do Not Merge Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[QUERY] Blob Trigger Function App: Will LogScan happen when it is connecting to a 2nd storage account?
1 participant