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

feat(events): introduce events fallbacks #3965

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

AlonZivony
Copy link
Collaborator

@AlonZivony AlonZivony commented Apr 8, 2024

1. Explain what the PR does

Introduce the concept of events failure because of dependencies.
Add events the ability to declare a fallback dependencies, to be used upon failure.
This allows events to implement not necessarily supported implementation,
for new kernels for example, with other implementation to cover unsupported scenarios.

2. Explain how to test it

3. Other comments

Introduce the concept of events failure because of dependencies.
Add events the ability to declare a fallback dependencies, to be used upon failure.
This allows events to implement not necessarily supported implementation,
for new kernels for example, with other implementation to cover unsupported scenarios.
Track dependencies on probes.
This makes it easier to understand when new probes are added or old ones removed.
Change the handling of the probes attach and detach to use the dependencies watchers.
This allows to handle correctly failure of events and future events updates.
@NDStrahilevitz
Copy link
Collaborator

IMO, if we're going by an approach where we can replace an entire set of dependency with another, then instead of having a recursive definition, each event should just have an array of definition so the map becomes map[events.ID][]EventDefinition. I think it would be slightly more readable, WDYT?

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.

None yet

2 participants