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

fix: data source registration after NewEngine #3342

Merged

Conversation

NDStrahilevitz
Copy link
Collaborator

@NDStrahilevitz NDStrahilevitz commented Jul 26, 2023

Author: Nadav Strahilevitz <nadav.strahilevitz@aquasec.com>
Date:   Wed Jul 26 15:03:21 2023 +0000

chore (engine): split Init from NewEngine

Previously data sources could not be registered after the NewEngine call
call and be used in signatures, due to the Init calls being made in
NewEngine.

Fix by moving the loadSignature and initial data source registers to
a new Init method from NewEngine.

In addition, export a method in tracee to prepare the builtin data
sources provided out of the box.

Fix #3341

Needs backport into v0.16.0 and v0.17.0

@rafaeldtinoco
Copy link
Contributor

Needs backport into v0.16.0 and v0.17.0

We only maintain the latest release (right @yanivagman ?)

@geyslan you're the release owner, up to you to approve, merge and cherry-pick.

Copy link
Contributor

@rafaeldtinoco rafaeldtinoco left a comment

Choose a reason for hiding this comment

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

LGTM and we agreed this is a change that can be cherry-picked in the latest release in our latest Tracee meeting.

@geyslan
Copy link
Member

geyslan commented Jul 26, 2023

Needs backport into v0.16.0 and v0.17.0

We only maintain the latest release (right @yanivagman ?)

@geyslan you're the release owner, up to you to approve, merge and cherry-pick.

@NDStrahilevitz, I'm waiting tests pass to get this merged.

Previously data sources could not be registered after the NewEngine call
call and be used in signatures, due to the Init calls being made in
NewEngine.

Fix by moving the loadSignature and initial data source registers to
a new Init method from NewEngine.

In addition, export a method in tracee to prepare the builtin data
sources provided out of the box.
@NDStrahilevitz NDStrahilevitz force-pushed the fix/register_data_source_after_new branch from eed3f60 to d588ce8 Compare July 27, 2023 11:12
@geyslan geyslan merged commit efa0ec4 into aquasecurity:main Jul 27, 2023
26 checks passed
geyslan pushed a commit to geyslan/tracee that referenced this pull request Jul 27, 2023
Previously data sources could not be registered after the NewEngine call
call and be used in signatures, due to the Init calls being made in
NewEngine.

Fix by moving the loadSignature and initial data source registers to
a new Init method from NewEngine.

In addition, export a method in tracee to prepare the builtin data
sources provided out of the box.

commit: efa0ec4 (main), cherry-pick
geyslan added a commit that referenced this pull request Jul 27, 2023
Previously data sources could not be registered after the NewEngine call
call and be used in signatures, due to the Init calls being made in
NewEngine.

Fix by moving the loadSignature and initial data source registers to
a new Init method from NewEngine.

In addition, export a method in tracee to prepare the builtin data
sources provided out of the box.

commit: efa0ec4 (main), cherry-pick

Co-authored-by: Nadav Strahilevitz <nadav.strahilevitz@aquasec.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Functionally can't register data sources after NewEngine
3 participants