update(userspace/falco): make plugin init config optional and add --plugin-info CLI option #2059
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
This PR brings two main contributions:
init_config
field optional infalco.yaml
. If not specified, Falco assumes an empty string to be passed as an empty configuration, which is what is used most commonly so far and also makes the config parsing process more robust--plugin-info
that prints detailed information regarding one individual plugin loaded through the Falco config. This allows printing info such as the init config schema or a list of suggested open parameters.Which issue(s) this PR fixes:
Special notes for your reviewer:
Example usage of the
--plugin-info
option (assuming thek8saudit
plugin is loaded):Does this PR introduce a user-facing change?: