[Tracking] Isolate libsinsp components from sinsp
This is a tracking issue for all works aiming to isolate the different libsinsp components from sinsp, as concerns raised in https://github.com/falcosecurity/libs/pull/2335 indicate that the work requires a more structured approach.
The work is organized by component.
- [ ] Threadinfo
- [x] https://github.com/falcosecurity/libs/pull/2342
- [x] https://github.com/falcosecurity/libs/pull/2344
- [x] https://github.com/falcosecurity/libs/pull/2345
- [x] https://github.com/falcosecurity/libs/pull/2350
- [x] https://github.com/falcosecurity/libs/pull/2347
- [x] https://github.com/falcosecurity/libs/pull/2351
- [x] https://github.com/falcosecurity/libs/pull/2335
- [ ] Thread manager
- [x] https://github.com/falcosecurity/libs/pull/2354
- [x] https://github.com/falcosecurity/libs/pull/2356
- [x] https://github.com/falcosecurity/libs/pull/2359
- [x] https://github.com/falcosecurity/libs/pull/2361
- [x] https://github.com/falcosecurity/libs/pull/2362
- [x] https://github.com/falcosecurity/libs/pull/2366
- [x] https://github.com/falcosecurity/libs/pull/2371
- [ ] User group manager
- [x] https://github.com/falcosecurity/libs/pull/2368
- [ ] Parser
- [x] https://github.com/falcosecurity/libs/pull/2374
- [ ] Sinsp event
- [x] https://github.com/falcosecurity/libs/pull/2377
- [ ] Misc
- [x] https://github.com/falcosecurity/libs/pull/2391
- [ ] https://github.com/falcosecurity/libs/pull/2402
/kind documentation
/milestone 0.22.0
@ekoops did a ton of work for 0.21.0 but it is not over yet!
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