In this article, we review ways in which the Clickhouse analytical database engine can be made to interoperate with Steampipe, for the purpose of retrieving additional data to be added to events that are stored on Clickhouse, without requiring to list the entirety of the extra data in advance.
Tag: Steampipe
In this article, we present a new Steampipe plugin that can provide access to a plain PostgreSQL database. This has been requested several times and current solutions are cumbersome. This plugin extends the reach of Steampipe’s queries to static (or not) data that is hosted on ordinary tables.
in this post, we start testing the Steampipe plugin that bridges to Terraform data sources with several random Terraform providers. We uncover a few bugs, and we find that the plugin (mostly) works as intended.
In this article we explore the Terraform Registry API, which hosts information about Terraform providers, in particular the URLs in which the actual provider binaries are hosted. We then implement a client for that API in our Steampipe plugin, so the plugin auto-downloads whichever Terraform provider has been requested by the user, at boot time. This makes the experience of configuring a Terraform provider in Steampipe a lot closer to that of configuring it on Terraform itself
In this article, we use Terraform data sources to automatically declare tables for a Steampipe plugin, and we forward queries that come in for each table to the corresponding Terraform datasource.
In this article, we query the Data Sources of Terraform plugins from a standalone Go program (i.e., not via the Terraform CLI). We can thus test and use a Terraform provider in isolation, and reuse the already-existing functionality of Data Sources in other programs, such as a Steampipe plugin.
In this article, we explore the way in which Terraform runs its plugins, AKA providers. We replicate the protocol in another program, and we run the Terraform DNS provider outside of Terraform. We extract its schema, which can tell us which credentials the provider needs, and also the data sources that it exposes, along with the fields that each data source has.
In this article, we start a new project: giving Steampipe access to any* Terraform datasource. This would allow a project to both effect changes in cloud infrastructure (by using Terraform) and verify or monitor those changes (by querying Steampipe), reusing code between both activities
In this article, we explore the traces&metrics functionality implemented in Steampipe. We also expose custom metrics from our own plugins. We also enhance Steampipe’s traces with custom tags and event logs, and even create new traces!
In this short article, we’ll explore the caching facilities available to a Steampipe plugin.