Pass a configuration filepath as an argument to the streampipe command. about steampipe HOT 9 CLOSED

We could add the ability to specify the config path but I'm not sure that it would solve your particular problem. The plugin configuration defines connections which are global - they are server-level objects, not client settings. A single Steampipe DB instance has the same connections for all clients. That means that if you want a different connection config for each user you would have to create a DB instance for each user. You can do this today using --install-dir, STEAMPIPE_INSTALL_DIR or the install_dir workspace argument.

An alternative is to create a connection for every user and set the search path on a per-client basis to default to "their" connection. This doesn't preclude them from using any other connection however, just sets the connection that would be used for unqualified queries. You could conceivably use Postgres permissions to lock this down, but you would have to implement that yourself. Steampipe creates a single steampipe user, as the Steampipe CLI is optimized for a single user.

You could also explore Turbot Pipes. Where Steampipe CLI is meant for a single person doing a single thing at a single point in time, Pipes is intended to allow many people doing many things over time.

from steampipe.

from steampipe.

I guess I misunderstood your request. It sounded like you wanted to share the same database instance from different clients, with different configurations for each. If you are going to start a separate DB instance for each user then it is reasonable to add a config path arg to the service start command. Is that what you are looking for?

As for the --install-dir, that needs to point to the equivalent of the ~/.steampipe directory. The drawback is that you would have to install the plugins in each of these instances.

from steampipe.

Exactly.
I would like to add a config path argument to the Steampipe command.
The steampipe instances aren't long-running instances as I intend calling it from a web server context (with Python's subprocess, then passing a config file containing the Stripe API key, that I created in that request cycle) and displaying the output in a dashboard.
Can I do this currently with Steampipe?

from steampipe.

When you say displaying output in a dashboard do you mean a Steampipe/Powerpipe dashboard or your own application's dashboard?

from steampipe.

If you are treating these instances as ephemeral and short-lived, and you are only accessing them through your own code on the back end, perhaps the SQLite Extensions or Export CLIs might be a better, more lightweight fit?

from steampipe.

When you say displaying output in a dashboard do you mean a Steampipe/Powerpipe dashboard or your own application's dashboard?

My application's dashboard

from steampipe.

If you are treating these instances as ephemeral and short-lived, and you are only accessing them through your own code on the back end, perhaps the SQLite Extensions or Export CLIs might be a better, more lightweight fit?

I think I will try the export CLI, I see it allows me to pass a --config flag. Which is fits what I am trying to accomplish.

from steampipe.

closing this issue - please raise another or get in touch via the steampipe community of you have further issues/questions

from steampipe.