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

x-pack/filebeat/input/cel: update function signature to new cel-go API #39011

Closed
efd6 opened this issue Apr 17, 2024 · 1 comment · Fixed by #39460
Closed

x-pack/filebeat/input/cel: update function signature to new cel-go API #39011

efd6 opened this issue Apr 17, 2024 · 1 comment · Fixed by #39460
Assignees
Labels
Team:Security-Service Integrations Security Service Integrations Team

Comments

@efd6
Copy link
Contributor

efd6 commented Apr 17, 2024

The current mito extention function definitions make use of the old definition mechanism which is complex and has some issues with compile-time type evaluation resulting in rejection of some valid programs. These issues can be fixed by moving to the new function definition API that came with cel-go v0.18.

A change is pending in the mito repo to make this shift. This will need to be integrated into beats and due to the significant change to the extension library, tested against a variety of integrations to ensure that the change does not introduce any regression.

@efd6 efd6 self-assigned this Apr 17, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 17, 2024
@efd6 efd6 added Team:Security-Service Integrations Security Service Integrations Team and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 17, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants