I've been thinking about this comment for a few hours now! I love it! I like building VS Code extensions and realized quickly the benefit of writing the logic in an LSP but I would never have thought to do the SSH config thing you describe.

I've now started a Makefile lsp since you've inspired me to think about the painful scenarios that LSP can solve if I think a bit wider.

Cheers for that!!

I actually started out using that. I wanted a debug UI to track messages which was the major driver in creating my own tbh

I wrote this for the infracost LSP so I could write multiple IDE extensions. Its not even really a language server, its just a neat way to parse the Terraform/Cloudformation and return diagnostics.

Language servers are cool!

thanks!

Thankfully, I finally had a reason to build an LSP (infracost LSP), so it motivated this and I'm really pleased with it

Yeah some times godoc comments look crap by necessity

But you don't have to add a docstring. Cases like this are worse than no docstring at all, because it wastes the reader's time.

If you add one, at least make the effort to provide some useful information. For example which is more severe: higher or lower numbers.

Every public item should have a docstring, even if it's just to indicate that there's nothing special about the item.

I disagree - you should have docstring and I don't think this is worse by having it... its just not ideal

Boilerplate docstrings are lint that spreads, and stale ones are worse, I've seen sevreity fields documented less clearly than the code they annotate.

To a certain extent I agree - I've worked on projects where a resource amounts to a rounding error in the overall cloud bill; for many organizations, cost is an important NFR for a project.

Going off the other threads of this post, how much engineers should know or care about billing seems to be open for debate; I think an engineer needs to appreciate that often cost is one of the many trade-offs that need to be accounted for

I just gave this a try with https://github.com/eksctl-io/eksctl/blob/main/examples/01-si...

ChatGPT gave me a decent chuck of terraform and running Infracost against it gave me a $515 monthly cost.

If you go to the settings of the plugin and get the absolute path of infracost binary then run

infracost breakdown --path .

in the dir with the terraform, does it give you a breakdown?

Hey Itay, thanks, and thanks for commenting, great to hear from you!!

The next step is certainly to look at the cloud account to get information on usage - this completes the picture of both for intended resources to create and what is already there.

Thanks for the feedback

Great feedback - thanks