examples VS cloud-pricing-api

It seems that kubernetesx never really got much traction, since I'm also having trouble finding any documentation / examples for it (except in the repo itself). For example, it's not even listed in https://github.com/pulumi/examples

From here, there's a bunch more you might think about next: writing more tests to cover the code we just added, exploring some additional flavors of testing in the docs, or having a look at a few examples. You'll find the full source for this walkthrough up on GitHub as well.

https://github.com/pulumi/examples: Lots of useful references in here. It's organized by [cloud]-[language]-* (so for example, aws-ts for AWS TypeScript) and many have good comments that explain what each piece is doing.

I've found the Python one to work well. I haven't used Go's. You can check out code examples for yourself: https://github.com/pulumi/examples. Pulumi programs are really just instantiations of classes/objects with key/value pairs that mirror the cloud provider's API, so it's not surprising that the code between languages look similar. It's interesting that you're not a fan of TypeScript though given that its language features work incredibly well for describing cloud infrastructure work. I would suggest reevaluating it as a language choice.

If you're already comfortable with Pulumi, and you just want to get up and running, I've set up a GitHub repo (complete with a Deploy with Pulumi button!) that should have all you need to get going. Just click the button, set a few configs (like your RSS server's administrative password, which will be stored as an encrypted Pulumi secret), and follow the prompts. Your shiny new server should be up and running within minutes.

There's a lot more you can do with integrations like this that we didn't cover: add more Lambda function handlers, have EventBridge target other AWS services (Step Functions might be a good one to try next), validate HTTP request bodies (with API Gateway models, to keep bad data from ever reaching EventBridge), and more. Hopefully this gives you sense of what's possible, though. And as promised, you'll find examples that use both versions of API Gateway in our examples repository on GitHub:

provisioners module is an implementation of Terraform provisioner in Pulumi, which allows us to copy files, run commands remotely on the EC2 instance. Refer to documentation.

Pulumi example projects https://github.com/pulumi/examples

u/ErikHumphrey yep, by default Infracost connects to our hosted Cloud Pricing API but you can self-host that part (which fetches the 3M+ prices from AWS+Azure+Google and self-updates), see https://www.infracost.io/docs/cloud_pricing_api/self_hosted/ and the "DISABLE_TELEMETRY" env variable that is mentioned in https://github.com/infracost/cloud-pricing-api

Infracost has two versions: a VSCode addon and a command line program. Both do the same thing: parse Terraform code, pull the current cost price points from a cloud pricing API, and output an estimate.

The complexity is crazy for sure. Around 10 years ago I started looking at cloud costs as part of my PhD - back then there were around 10,000 price points that I was scraping manually, today there are more than 3 million prices between AWS, Azure and Google that we're fetching in https://github.com/infracost/cloud-pricing-api

yup, checkout this example. Happy to help with the other filters you might need, I spend a lot of time exploring pricing params