-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[azureeventhubreceiver] Migrate to new AzureSDK #33134
[azureeventhubreceiver] Migrate to new AzureSDK #33134
Conversation
Without this change the concurrent case was broken for some reason. Regardless, the divergence in paths used is the approach strongly recommended by the SDK docs.
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a great addition. Once the build is fixed I think this is ready to go from my perspective.
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Description:
This is an enhancement to the
azureeventhubreceiver
, which migrates code to use the current library as recommended by Azure in the SDK migration guide for EventHubs in Go.azureeventhubreceiver
was initially developed whenazure-event-hubs-go
was the preferred package. This has superseded by theazeventhubs
package in theAzure/azure-sdk-for-go
repo. See the migration guide for the package.Link to tracking Issue: #31252
Testing: Unit tests are updated and I have done some manual testing in development with Azure payloads.
Documentation: No additional documentation as there's no change for Collector users.