v0.4.1

Bug fixes

• Fix issue where the --arg flag was not working for control and query runs. (#439)
• Fix data inconsistency issue in snapshot output when the same control was included in multiple benchmarks. (#436)

v0.3.2-alpha.202406111022

version

v0.4.1-alpha.202406101636

Update version

v0.4.0

Whats new

• Update JSON output to handle duplicate column names - append a unique suffix to duplicate column names. (#375)
• Update snapshot schema and dashboard event schema versions to 20240607. (#406)

Bug fixes

• When generating a snapshot from a benchmark run, the row data is empty any of the rows are in error. (#366)
• Update mod install to only install or update mods which are command targets (and their dependencies). Set default pull mode for install is latest if there is a target, and minimal if no target is given. (#381)
• Fix incorrect help message for output in powerpipe benchmark/control run. (#367)
• Fix issue where POWERPIPE_PORT env var was not being honoured. (#362)
• Update timing metadata output to rename duration field to duration_ms for consistency with steampipe. (#368)
• Dashboard graph should not crash if an invalid edge category color is provided. (#364)
• Dashboard flow/hierarchy components should show panel controls. (#363)

v0.3.2-rc.202406051523

Remove sps references from help messages

v0.3.1

Update pipe-fittings to v1.3.3

Fix mod require block being rewritten incorrectly when installing a mod if the require block exists but does not contain mod requirements. 
Fix status display for updating transitive dependencies

v0.3.0

Whats new

• Add support for installing mods from a branch or from the local file system. (#285)

To install from a branch:

powerpipe mod install github.com/turbot/steampipe-mod-aws-well-architected#main

To reference a mod in the local file system:

powerpipe mod install ../mods/local_mod_folder

• Add --pull flag to mod, dashboard and benchmark commands to control the mod update strategy. (#352). Possible update strategies are:

  • full - check branch and tags for both latest and accuracy
  • latest - update everything to latest, but only branches - not tags - are commit checked (which is the same as latest)
  • development - update branches and broken constraints to latest, leave satisfied constraints unchanged
  • minimal - only update broken constraints, do not check branches for new commits

v0.3.0-rc.202405140800

skip test

v0.3.0-rc.202405101222

Fix NewInstallOpts

v0.3.0-alpha.202405071844

go.mod