falcosecurity/event-generator suite test
Run 'event-generator suite test' over a folder of YAML test descriptions against an already-running Falco, and expose the suite report plus the expected passing-test count so the caller can verify the outcome. The caller owns Falco's lifecycle and must configure it as described in https://github.com/falcosecurity/event-generator/blob/main/docs/event-generator_suite_test.md#falco-configuration. The event-generator binary and the container base image are built from this action's own checked-out source, so pinning the action to a commit SHA pins the whole toolchain.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| tests-dir | Folder of YAML test descriptions to run, resolved relative to github.workspace (the caller's checked-out repository). | no | e2e_tests/evtgen_suite |
| http-address | host:port the event-generator alert retriever binds to. The caller's Falco must send JSON-encoded alerts to this endpoint, so alerts reach the retriever and can be correlated back to tests. | no | localhost:8080 |
| report-format | Suite report format: 'text', 'json' or 'yaml'. | no | json |
| timeout | Maximum duration of the whole suite test run, as a Go duration (e.g. 10m). | no | 10m |
| event-generator-image | Optional event-generator container image, used both as --container-base-image (for tests that declare context.container) and as the source of the host-side binary that runs the suite (extracted from it), so both use the same build. When empty, the image is built from this action's checked-out source so it matches the pinned action SHA. | no | "" |
| sudo | sudo command. Set to empty on runners where sudo is unavailable or unnecessary. | no | sudo |
Outputs
| name | description |
|---|---|
| report | Absolute path to the suite test report file. |
| expected-tests | Number of tests that are expected to pass. |