Skip to content

Allow to use otelcol inputs in integration packages#1091

Merged
jsoriano merged 6 commits intoelastic:mainfrom
jsoriano:otelcol-integration
Feb 23, 2026
Merged

Allow to use otelcol inputs in integration packages#1091
jsoriano merged 6 commits intoelastic:mainfrom
jsoriano:otelcol-integration

Conversation

@jsoriano
Copy link
Copy Markdown
Member

@jsoriano jsoriano commented Feb 17, 2026

What does this PR do?

Fixes #1085

Allow to use otelcol inputs and dynamic_signal_types in integration packages starting on 3.6.0.

otelcol was 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

Related issues

@jsoriano jsoriano self-assigned this Feb 17, 2026
@jsoriano jsoriano requested a review from a team as a code owner February 17, 2026 13:00
teresaromero
teresaromero previously approved these changes Feb 18, 2026
…nal_types.go

Co-authored-by: Tere <romero.teresa@protonmail.com>
teresaromero
teresaromero previously approved these changes Feb 18, 2026
mrodm
mrodm previously approved these changes Feb 18, 2026
@jsoriano jsoriano dismissed stale reviews from mrodm and teresaromero via 7c6f6d1 February 18, 2026 17:25
mrodm
mrodm previously approved these changes Feb 19, 2026
teresaromero
teresaromero previously approved these changes Feb 19, 2026
@jsoriano jsoriano dismissed stale reviews from teresaromero and mrodm via 19ee161 February 20, 2026 10:00
Comment on lines +674 to +678
- op: add
path: "/properties/streams/items/properties/input"
value:
not:
const: otelcol
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There this is patch, but this is not removed from the spec now in this file.

https://github.com/elastic/package-spec/pull/1091/changes#diff-6df76cc1b8f4eb6c07ebbd27a8623ea7e958834bff11c4ffe644ec6d22bad2dfL576-L577

        properties:
          input:
            type: string
            examples:
            - aws/metrics
            - s3
            - file
            not:
              const: otelcol

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, I think I broke this in the merge.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or not, this was actually wrong before the merge. Fixed in e556170, with tests cases that would have catch this.

Good catch, thanks!

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

cc @jsoriano

@jsoriano jsoriano merged commit 68b63d2 into elastic:main Feb 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Change Proposal] Allow the use of otelcol inputs in integration packages

4 participants