Expose the Falco Engine version through the gRPC Version API #1269
Comments
|
The need for this emerged while reviewing this. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Issues labeled "cncf", "roadmap" and "help wanted" will not be automatically closed. Please refer to a maintainer to get such label added if you think this should be kept open. |
|
/help |
|
@leogr: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via /~https://github.com/falcosecurity/community. /lifecycle stale |
|
/assign nibalizer |
Fixes falcosecurity#1269 Add two new fields in the version service for falco's engine version and the checksum of all of the fields it understands. This will require rebuilding/re-releasing all the clients. Signed-off-by: Spencer Krum <nibz@spencerkrum.com>
Fixes falcosecurity#1269 Add two new fields in the version service for falco's engine version and the checksum of all of the fields it understands. This will require rebuilding/re-releasing all the clients. Signed-off-by: Spencer Krum <nibz@spencerkrum.com>
Fixes #1269 Add two new fields in the version service for falco's engine version and the checksum of all of the fields it understands. This will require rebuilding/re-releasing all the clients. Signed-off-by: Spencer Krum <nibz@spencerkrum.com>
Motivation
Rules depend on the Falco Engine version (and the fields a specific version supports) in order to work.
It can be useful to know this version value (and also the fields and rules a version supports) in order to create external tooling (eg., test harness) aware of such knowledge and behaving accordingly.
Feature
Expose the Falco Engine version through the existing gRPC Version API.
Alternatives
Read the Falco Engine version from built files or from source files. Not ideal because it implies a dependency of artifacts on them, imho.
The text was updated successfully, but these errors were encountered: