libs
libs copied to clipboard
falcosecurity
Enforce compatibility for the API and schema versions for the drivers
Motivation
After #436, it became apparent the minimum API and schema versions for the drivers need to be manually and individually bumped for the userspace and driver components. This, even if it is not a great amount of work, can potentially lead to the libraries breaking if the major version is changed on the drivers and not in userspace. Because the bumping of versions needs to be kept manual, an automated check to ensure the bump is correct and compatible should be put in place.
We should also look into adding checks for conditions where the versions should've been bumped but didn't (though this might be a bit more complicated IMO).
Feature
An automated check schema and API compatibility should be implemented in CI. Could probably be as simple as having a unit test that runs check_api_compatibility with the minimum versions configured in the userspace component and the version set in the drivers.
Alternatives
More complex stuff like running sinsp-example with a driver and ensure it starts properly can also be considered.
Additional context
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
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
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.