#Steam bundle files install#

This means you essentially run the same list API calls 48 times! When using aggregators, it is especially important to: Consider as an example and aggregator that includes 3 AWS connections, where each connection queries 16 regions.

Like any other steampipe connection, they query APIs and are subject to API limits and throttling. Note that for standard Steampipe plugins that are installed from the Steampipe Hub, the short name may be used, and will use latest if the tag is omitted, thus the following are equivalent:Īggregators are powerful, but they are not infinitely scalable. The plugin argument should contain the path to the plugin relative to the plugin directory. Additional arguments are plugin-specific, and are used to determine the scope, credentials, and other configuration items. Each connection must contain a single plugin argument that specifies which plugin to use in this connection. The connection name will be used as the Postgres schema name in the Steampipe database. Steampipe config files use HCL Syntax, with connections defined in a connection block. This file contains a single aws connection definition that configures the plugin to use the same configuration as the aws cli.

#Steam bundle files install#

In addition, it may contain commented out sample connections for common configurations.įor example, the aws plugin will install the ~/.steampipe/config/aws.spc configuration file. This file usually contains a single connection, configured in such as way as to to dynamically match the configuration of the associated CLI. Upon installation, a plugin may install a default configuration file, typically named. A config file may contain multiple connections. Steampipe will load ALL configuration files from ~/.steampipe/config that have a. Connection configuration files StructureĬonnection configurations are defined using HCL in one or more Steampipe config files. Note that there is nothing special about the default connection, other than that it is created by default on plugin install - You can delete or rename this connection, or modify its configuration options (via the configuration file). select * from azure_compute_virtual_machine in the azure connection works the same as az vm list.select * from aws_ec2_instance in the aws connection will target the same account/region as aws ec2 describe-instances.This means that by default, Steampipe 'just works' per the CLI: Usually, this entails evaluating environment variables ( AWS_PROFILE, AWS_REGION, AZURE_SUBSCRIPTION_ID, etc) and configuration files - The details vary by provider. This connection should be dynamic, and use the same scope and credentials that would be used for the equivalent CLI. Many plugins will create a default connection when they are installed. An aws connection contains tables for a single AWS account.A google connection contains tables for a single GCP project.An azure connection contains tables for a single Azure subscription.The boundary/scope of the connection varies by plugin, but is typically aligned with the vendor's cli tool and/or api. Each connection is represented as a distinct Postgres schema.Ī connection is associated with a single plugin type.

A Steampipe connection represents a set of tables for a single data source.