Skip to content
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

Draft
wants to merge 33 commits into
base: main
Choose a base branch
from

Conversation

nslaughter
Copy link
Contributor

@nslaughter nslaughter commented May 20, 2024

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 when azure-event-hubs-go was the preferred package. This has superseded by the azeventhubs package in the Azure/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.

@nslaughter nslaughter force-pushed the nslaughter/migrate-azure-sdk-for-eventhub branch from 85c2d0a to 9bf9c12 Compare May 23, 2024 17:59
Copy link
Contributor

github-actions bot commented Jun 7, 2024

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jun 7, 2024
@github-actions github-actions bot removed the Stale label Jun 12, 2024
Copy link
Contributor

@cparkins cparkins left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants