You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
Run a custom plugin which doesn't specify the result-format field. You can use sonobuoy gen to copy the e2e plugin definition and clear that field (for one concrete example).
This results in no sonobuoy_results.yaml file being produced and sonobuoy results command being useless for it.
What did you expect to happen:
Without more information to go on, we should assume the raw format, which just means that the server will iterate over the resulting files and save breadcrumbs to them. This would allow the CLI to navigate to those result files easily and report about them.
Environment:
Sonobuoy version: v0.15.0 (master)
The text was updated successfully, but these errors were encountered:
When unset (or invalid), currently no post-processing is done which
means that users won't find the sonobuoy_results.yaml file.
By defaulting to 'raw' we make users immediately get a benefit from
the post-processing regardless of if they take extra steps to
customize the type/output.
Fixes#820
Signed-off-by: John Schnake <jschnake@vmware.com>
What steps did you take and what happened:
Run a custom plugin which doesn't specify the
result-format
field. You can usesonobuoy gen
to copy thee2e
plugin definition and clear that field (for one concrete example).This results in no
sonobuoy_results.yaml
file being produced andsonobuoy results
command being useless for it.What did you expect to happen:
Without more information to go on, we should assume the
raw
format, which just means that the server will iterate over the resulting files and save breadcrumbs to them. This would allow the CLI to navigate to those result files easily and report about them.Environment:
The text was updated successfully, but these errors were encountered: