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

[8.x](backport #42794) [azure-eventhub] Update sdk/messaging/azeventhubs to v1.3.0 #42972

Open
wants to merge 2 commits into
base: 8.x
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 1, 2025

Proposed commit message

Upgrade the sdk/messaging/azeventhubs package to the latest stable version v1.3.0.

This package is the core library of the modern Event Hub SDK we use in the azure-eventhub input v2. From v1.2.1 to v1.3.0 we get several bug fixes and a new TCP proxies with AMQP feature.

Author's Checklist

  • Run a input v2 smoke test ingesting activity logs

How to test this PR locally

# x-pack/filebeat/modules.d/azure.yml
- module: azure
  # All logs
  activitylogs:
    enabled: true
    var:
      # eventhub name containing the activity logs, overwrite he default value if the logs are exported in a different eventhub
      eventhub: "logs"
      # consumer group name that has access to the event hub, we advise creating a dedicated consumer group for the azure module
      consumer_group: "$Default"
      # the connection string required to communicate with Event Hubs, steps to generate one here https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string
      connection_string: '${EVENTHUB_CONNECTION_STRING:""}'
      # the name of the storage account the state/offsets will be stored and updated
      storage_account: '${EVENTHUB_STORAGE_ACCOUNT:""}'
      # the name of the storage account container you would like to store the offset information in.
      # storage_account_container: ""
      # the storage account key, this key will be used to authorize access to data in your storage account
      storage_account_key: '${EVENTHUB_STORAGE_ACCOUNT_KEY:""}'
      # the connection string required to communicate with the storage account, steps to generate one here https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal
      storage_account_connection_string: '${EVENTHUB_STORAGE_ACCOUNT_CONNECTION_STRING:""}'
      # the processor version to use, v1 is the legacy processor and v2 is the new processor
      processor_version: v2

This is an automatic backport of pull request #42794 done by [Mergify](https://mergify.com).

Upgrade the `sdk/messaging/azeventhubs` package to the latest stable version v1.3.0.

This package is the core library of the modern Event Hub SDK we use in the `azure-eventhub` input v2. From v1.2.1 to v1.3.0 we get several bug fixes and a new TCP proxies with AMQP feature.

(cherry picked from commit a964b89)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify bot requested a review from a team as a code owner March 1, 2025 18:39
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 1, 2025
@mergify mergify bot assigned zmoog Mar 1, 2025
Copy link
Contributor Author

mergify bot commented Mar 1, 2025

Cherry-pick of a964b89 has failed:

On branch mergify/bp/8.x/pr-42794
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit a964b89e5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 1, 2025
@github-actions github-actions bot added Team:obs-ds-hosted-services Label for the Observability Hosted Services team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team input:azure-eventhub labels Mar 1, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 1, 2025
@zmoog
Copy link
Contributor

zmoog commented Mar 2, 2025

/test

Copy link
Contributor Author

mergify bot commented Mar 3, 2025

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request input:azure-eventhub Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team Team:obs-ds-hosted-services Label for the Observability Hosted Services team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants