Releases: turbot/steampipe
Releases · turbot/steampipe
v0.24.0
Whats new
- Add ability to configure plugin startup timeout. (#4320)
- Install FDW and embedded postgres database from GHCR instead of GCP. (#4344)
- Update query JSON output format to add a
columns
property containing the column information. This allows us to handle duplicate column names by appending a unique suffix to duplicate column name (#4317)
Existing query JSON format:
$ steampipe query "select account_id, arn from aws_account" --output json
{
"rows": [
{
"account_id": "123456789012",
"arn": "arn:aws:::123456789012"
}
]
}
New query JSON format(with new columns
property):
$ steampipe query "select account_id, arn from aws_account" --output json
{
"columns": [
{
"name": "account_id",
"data_type": "text"
},
{
"name": "arn",
"data_type": "text"
}
],
"rows": [
{
"account_id": "123456789012",
"arn": "arn:aws:::123456789012"
}
]
}
Bug fixes
- Fix issue where plugin manager was incorrectly reporting a shutdown. (#4365)
v0.23.5
v0.23.5-rc.0
v0.23.5-rc.0
v0.23.4
v0.23.3
Bug fixes
- When installing plugins, do not use local docker config for credential store if the plugin is being installed from GHCR, enabling installation from GHCR to work even if docker-credential-desktop not in PATH. (#4323)
- Fix issue where steampipe returned 0 exit code even if failed to export snapshot. (#4276)
- Query command should support legacy 'true' and 'false' for --timing flag. (#4282)
- Fix issue where sps output is not working. (#4297)
- When loading creating connection plugins, return connections successfully created even if some connections fail, due to config not being available. (#474)
- Show scan info in query JSON output only when timing config is verbose. (#4292)
v0.23.2
Bug fixes
- Update FDW to 1.11.2 to remove unnecessary NOTICE level log messages. (turbot/steampipe-postgres-fdw#469)
v0.23.1
v0.23.0
Whats new
- Add support for connection key columns. (#768)
A connection key column
defines a column that has a value which maps 1-1 to a Steampipe connection
and so can be used to filter connections when executing an aggregator query.
These columns are treated as (optional) KeyColumns. This means they are taken into account in the query planning.
- Add support for pushing down sort order. (#447)
- Update limit pushdown logic to push down the limit if all sort clauses are pushed down. (#458)
- Add support for
WHERE column=val1 OR column=val2 OR column=val3...
- Adds support for verbose timing information. (#4244)
- Migrate from plugin registry from GCP to GHCR. (#4232)
Bug fixes
v0.23.0-rc.0
v0.23.0-rc.0
v0.23.0-alpha.7
v0.23.0-alpha.7