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 #42388) fix: keep otelbeat package self contained #42414

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 23, 2025

Proposed commit message

elasticsearch output package importing otelbeat is causing downstream clients of beats to import otel libraries as well, polluting the module graph.

do not leak otelbeat package and keep it self-contained

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.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs


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

elasticsearch output package importing otelbeat is causing downstream clients of
beats to import otel libraries as well, polluting the module graph.

do not leak otelbeat package and keep it self-contained

(cherry picked from commit 6be7c82)
@mergify mergify bot added the backport label Jan 23, 2025
@mergify mergify bot requested a review from a team as a code owner January 23, 2025 21:48
@mergify mergify bot requested review from leehinman and khushijain21 and removed request for a team January 23, 2025 21:48
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 23, 2025
@botelastic
Copy link

botelastic bot commented Jan 23, 2025

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

@kruskall kruskall merged commit 16c7ebd into 8.x Jan 24, 2025
142 checks passed
@kruskall kruskall deleted the mergify/bp/8.x/pr-42388 branch January 24, 2025 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport bugfix needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant