Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export does not merge benchmark results when running multiple benchmark checks in one steampipe command #2380

Closed
sfunkernw opened this issue Aug 26, 2022 · 2 comments · Fixed by #3779
Assignees
Labels
bug Something isn't working

Comments

@sfunkernw
Copy link

Describe the bug

Export does not merge benchmark results when running multiple benchmark checks in one steampipe command.

Steampipe version (steampipe -v)
steampipe version 0.16.0

Plugin version (steampipe plugin list)

  • hub.steampipe.io/plugins/turbot/aws@latest 0.74.1
  • hub.steampipe.io/plugins/turbot/steampipe@latest 0.5.0

To reproduce

steampipe check aws_compliance.benchmark.cis_v140 aws_compliance.benchmark.foundational_security aws_compliance.benchmark.other --export sp-cis-foundational-other-compliance-mod.json --max-parallel 5

This command runs properly all 3 benchmarks sequentially, but in the output file sp-cis-foundational-other-compliance-mod.json only the JSON formatted output of the last benchmark (aws_compliance.benchmark.other) is included.

Expected behavior

I would expect that the output of all 3 executed benchmarks end up in the exported output file.
In the case of the JSON output, expect to have have in the root object the sum of the status attributes for all benchmarks and in the top level groups array, I expect to have the 3 benchmark groups included as array elements.

Additional context

This behavior seems to be the same for the other formats (CSV etc.) as well.

Please note, whoever has the same problem, you could simply run the 3 benchmarks after each other and merge the results manually as described in my expected behavior.

@sfunkernw sfunkernw added the bug Something isn't working label Aug 26, 2022
@cbruno10 cbruno10 transferred this issue from turbot/steampipe-mod-aws-compliance Aug 26, 2022
@cbruno10
Copy link
Contributor

@sfunkernw I've transferred this issue to the Steampipe repo, as this issue looks to be about more overall CLI behavior than one specific to the AWS Compliance mod. If you have any other questions though, please let us know.

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label Sep 13, 2023
@pskrbasu pskrbasu removed the stale No recent activity has been detected on this issue/PR and it will be closed label Sep 13, 2023
@binaek binaek linked a pull request Sep 21, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants