Closed jasondellaluce closed 1 year ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Motivation
In order to develop plugins with event sourcing capability, developers need to provide a custom implementation of the
falcosecurity::event_sourcer::instance
interface, usually with the only purpose of overriding itsnext()
method.We had a similar situation with the Go SDK (see: https://github.com/falcosecurity/plugin-sdk-go/pull/50).
Feature
Having a prebuilt and SDK-provided implementation of
falcosecurity::event_sourcer::instance
that makes use of more high-level constructs and make life easier to plugin developers. A good candidate could be a "functional" pattern like the pull model of the Go SDK.