Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
steampipe-plugin-linode
Use SQL to instantly query instances, domains and more from Linode. Open source CLI. No DB required.
-
steampipe-plugin-oci
Use SQL to instantly query Oracle Cloud resources across regions and accounts. Open source CLI. No DB required.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Interesting how it implemented under-the-hood. Does it use cloudquery (https://github.com/cloudquery/cloudquery) or steampipe (https://github.com/turbot/steampipe) under-the-hood or does it implement everything from scratch.
Disclaimer: Im the founder of CloudQuery.
I get why you would want to do select * from infra, but not sure I understand why you would want to do "insert * into infra" and not use something like terraform? interested in hearing the use-case.
Interesting how it implemented under-the-hood. Does it use cloudquery (https://github.com/cloudquery/cloudquery) or steampipe (https://github.com/turbot/steampipe) under-the-hood or does it implement everything from scratch.
Disclaimer: Im the founder of CloudQuery.
I get why you would want to do select * from infra, but not sure I understand why you would want to do "insert * into infra" and not use something like terraform? interested in hearing the use-case.
Both seem to have reasonable Go SDK libraries, so it should be easy to create new plugins for them. I've added them to our internal backlog, but all our plugins are open source if you'd like to try building it yourself! The Linode plugin is a simple, similar example to use as a starting point [1]. We also have docs for writing plugins [2].
1 - https://github.com/turbot/steampipe-plugin-linode
true, but the tooling and workflow remains the same.
Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config.
I'm exploring using CUE (https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer