Allow to use otelcol inputs in integration packages#1091
Open
jsoriano wants to merge 2 commits intoelastic:mainfrom
Open
Allow to use otelcol inputs in integration packages#1091jsoriano wants to merge 2 commits intoelastic:mainfrom
jsoriano wants to merge 2 commits intoelastic:mainfrom
Conversation
💚 Build Succeeded
cc @jsoriano |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes #1085
Allow to use
otelcolinputs anddynamic_signal_typesin integration packages starting on 3.6.0.otelcolwas supported for input packages since 3.5.0.Assisted by Copilot
Why is it important?
It is going to be possible to make OTel integrations depend on OTel input packages. After combining them they may include OTel configurations and use otelcol inputs.
Checklist
test/packagesthat prove my change is effective.spec/changelog.yml.Related issues