From 5b79918723c1709e5a002f93c2c9071139607652 Mon Sep 17 00:00:00 2001 From: cbruno10 Date: Tue, 17 Jun 2025 15:05:21 -0400 Subject: [PATCH] Minor fixes for default Tailpipe DB --- docs/run/index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/run/index.md b/docs/run/index.md index 900c04f..2f23cdb 100644 --- a/docs/run/index.md +++ b/docs/run/index.md @@ -24,8 +24,8 @@ If you run Powerpipe in **Server Mode** mode, Powerpipe will run a dashboard ser ## Selecting a database -Most public mods are written without specifying a `database` on each query. As a result, all queries in the mod run against the 'active' database. For Steampipe, the active database is `postgres://steampipe@localhost:9193/steampipe`, thus Powerpipe will run against a local Steampipe instance. For Powerpipe, it's `duckdb:~/.tailpipe/data/default/tailpipe.db`. -` +Most public mods are written without specifying a `database` on each query. As a result, all queries in the mod run against the 'active' database. For Steampipe, the active database is `postgres://steampipe@localhost:9193/steampipe`, thus Powerpipe will run against a local Steampipe instance. For Tailpipe, it's `duckdb:~/.tailpipe/data/default/tailpipe.db`. + Some mods allow you to [set the database via a variable](/docs/build/mod-database). In this case, you can pass the connection to the variable when you run a powerpipe command: ```bash @@ -76,5 +76,3 @@ powerpipe benchmark run cis_v150 --search-path-prefix aws_connection_2 ``` [Steampipe](https://steampipe.io) creates a schema for each connection and aggregator, and understanding how the search path works is important when using Steampipe and Powerpipe. See the [Using search_path to target connections and aggregators](https://steampipe.io/docs/guides/search-path) guide for more information. - -