Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Refactors filter fields and rules to use the new module.* or dll.* fields. Backward compatibility with old fields is guaranteed.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area evasion

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


@rabbitstack rabbitstack force-pushed the refactor-image-fields branch 2 times, most recently from 877855e to 058eddb Compare January 27, 2026 17:46
@rabbitstack rabbitstack force-pushed the refactor-image-fields branch 2 times, most recently from 4c01cd3 to 56d2c77 Compare January 28, 2026 10:41
@rabbitstack rabbitstack merged commit 1ccb7b3 into master Jan 28, 2026
10 of 11 checks passed
@rabbitstack rabbitstack deleted the refactor-image-fields branch January 28, 2026 12:14
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.

1 participant