You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we require -o option:parse-arguments for signatures to function properly. This makes both the signatures and the event pipeline less efficient.
As a first step, let's remove argument parsing and use the raw arguments values in signatures.
This means we should update the golang signatures to use the libbpfgo consts and remove parse-arguments from being enabled by default with the pipeline. libbpfgo already have argument parsing helpers in a separate module so they can be used as enum values in signatures.
Currently we require
-o option:parse-arguments
for signatures to function properly. This makes both the signatures and the event pipeline less efficient.As a first step, let's remove argument parsing and use the raw arguments values in signatures.
This means we should update the golang signatures to use the libbpfgo consts and remove
parse-arguments
from being enabled by default with the pipeline. libbpfgo already have argument parsing helpers in a separate module so they can be used as enum values in signatures.Next steps (not part of this issue) include:
Find a way to export libbpfgo constants to rego and cel-goAdd a way to keep parsed arguments for cases where REGO signatures are wanted (Parse argument in a separate argument instead of inline #3008).The text was updated successfully, but these errors were encountered: