johnsmyth
commented
6 months ago 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.
aitoehigie
kaidaguerre
Is your feature request related to a problem? Please describe. I'm always frustrated when I cannot dynamically pass the Steampipe configuration file path (spc file) as an argument to the Steampipe command. This limitation prevents me from seamlessly integrating Steampipe into my web application where each user supplies their API tokens, and the configuration needs to be generated on the fly.
Describe the solution you'd like I would like the ability to pass the Steampipe configuration file path (spc file) as an argument to the Steampipe command. This enhancement would allow me to dynamically generate the configuration file for each user in my web application context, ensuring that each user's API tokens are used for querying with Steampipe.
Describe alternatives you've considered One alternative solution could be to set up separate Steampipe instances for each user, each with their own pre-configured spc file. However, this approach would be less scalable and would require significant overhead in managing multiple instances.
Additional context This feature would greatly enhance the flexibility and usability of Steampipe in web application contexts, enabling seamless integration with user-specific API tokens and configurations. It would simplify the deployment and management of Steampipe in multi-user environments and improve the overall user experience.