Live data from Hacker News

Cloud Infrastructure as SQL

iasql.com

11–20 of 113 posts

Re: Cloud Infrastructure as SQL

#11
Steampipe (https://steampipe.io) is an open source CLI to query cloud infrastructure using SQL (e.g. AWS, GitHub, Slack, k8s, etc). It also has a HCL language to define security benchmarks and controls (e.g. AWS CIS, etc).

We are a Postgres FDW under the hood with Go-based plugins, so write would be possible, but we've chosen to focus on read only so far. Definitely interested to see how you approach create, update and delete in the SQL model!

Notes: Not related to iasql. I'm a lead on the Steampipe project.

Re: Cloud Infrastructure as SQL

#12

Steampipe ( https://steampipe.io ) is an open source CLI to query cloud infrastructure using SQL (e.g. AWS, GitHub, Slack, k8s, etc). It also has a HCL language to define security benchmarks and controls (e.g. AWS CIS, etc). We are a Postgres FDW under the hood with Go-based plugins, so write would be possible, but we've chosen to focus on read only so far. Definitely interested to see how you approach create, update…

Neat. Does that use steampipe services/API under the hood, or does it consume the AWS/GigHub APIs/... directly?

Re: Cloud Infrastructure as SQL

#13

What problem does this solve, as opposed to a git repositories? To me, declarative infrastructure management is incredibly important in order to reason about a deployment. Even though under the hood, yes, everything is stateful, it’s something I want abstracted away, not as a primary way of interacting with my infrastructure. I guess what I’m asking is what the canonical use case / target user of this is.

[deleted]

Re: Cloud Infrastructure as SQL

#14

Steampipe ( https://steampipe.io ) is an open source CLI to query cloud infrastructure using SQL (e.g. AWS, GitHub, Slack, k8s, etc). It also has a HCL language to define security benchmarks and controls (e.g. AWS CIS, etc). We are a Postgres FDW under the hood with Go-based plugins, so write would be possible, but we've chosen to focus on read only so far. Definitely interested to see how you approach create, update…

Neat. Does that use steampipe services/API under the hood, or does it consume the AWS/GigHub APIs/... directly?

It talks directly to the cloud provider APIs. Plugins are written in go-lang (similar to Terraform providers).

OSS plugins - https://github.com/topics/steampipe-plugin

Docs - https://hub.steampipe.io/plugins

Re: Cloud Infrastructure as SQL

#15

Earlier quoted context omitted.

Neat. Does that use steampipe services/API under the hood, or does it consume the AWS/GigHub APIs/... directly?

It talks directly to the cloud provider APIs. Plugins are written in go-lang (similar to Terraform providers). OSS plugins - https://github.com/topics/steampipe-plugin Docs - https://hub.steampipe.io/plugins

WOOT! That's awesome.

Re: Cloud Infrastructure as SQL

#16
This has absolutely no relevance to me but that SQL snippet just bugs the hell out of me. I can't fathom why you would do a subquery in the from section and then not utilize a join. You're just bringing 2 datasets and letting them sit side by side, why not just move the subquery to the select section? Execution plan should result the same so I guess this is just a preference thing?

Re: Cloud Infrastructure as SQL

#17

This has absolutely no relevance to me but that SQL snippet just bugs the hell out of me. I can't fathom why you would do a subquery in the from section and then not utilize a join. You're just bringing 2 datasets and letting them sit side by side, why not just move the subquery to the select section? Execution plan should result the same so I guess this is just a preference thing?

It's using an implied cross join so each image is deployed onto a t2.micro

Re: Cloud Infrastructure as SQL

#18
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.

Re: Cloud Infrastructure as SQL

#19

This has absolutely no relevance to me but that SQL snippet just bugs the hell out of me. I can't fathom why you would do a subquery in the from section and then not utilize a join. You're just bringing 2 datasets and letting them sit side by side, why not just move the subquery to the select section? Execution plan should result the same so I guess this is just a preference thing?

It's using an implied cross join so each image is deployed onto a t2.micro

Ahh, gotcha. I appreciate the response there as I wasn't aware of that notation and even then I can't think of any time I've used a cross join. Not sure which syntax I would use personally.
Post reply on HN