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.14](backport #38861) filebeat/azure/azureeventhub: upgrade azure-event-hubs-go and azure-storage-blob-go dependencies #39290

Merged
merged 3 commits into from
May 1, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 30, 2024

Proposed commit message

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs


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

…torage-blob-go dependencies (#38861)

* filebeat/azure/azureeventhub: upgrade azure azure-event-hubs-go and azure-storage-blob-go dependencies

Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>

* add the changelog record

Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>

---------

Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
(cherry picked from commit 9841e00)
@mergify mergify bot requested a review from a team as a code owner April 30, 2024 08:41
@mergify mergify bot added the backport label Apr 30, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@botelastic
Copy link

botelastic bot commented Apr 30, 2024

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 30, 2024

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 180 min 37 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@tetianakravchenko
Copy link
Contributor

@cmacknz can you please review this backport PR? (backport of the #38861 that you've approved)

@cmacknz
Copy link
Member

cmacknz commented May 1, 2024

You should be able to approve this yourself, for backports the requirement is only that someone must have looked and approved. It doesn't require a codeowner reviewer.

Try it and if it doesn't work I'll take care of it.

@tetianakravchenko tetianakravchenko merged commit 468dc26 into 8.14 May 1, 2024
211 checks passed
@tetianakravchenko tetianakravchenko deleted the mergify/bp/8.14/pr-38861 branch May 1, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants