examples VS pulumi-tf-provider-boilerplate

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

I'm interested in how to take existing high-quality Terraform Providers and convert them into Pulumi providers. Can you discuss the future roadmap for this project and any others around this effort.

The documentation on https://github.com/pulumi/pulumi-tf-provider-boilerplate would benefit from more examples and further explanation. I had to reverse engineer the pulumi-aws provider to be able to wrap an existing TF provider.

> If Pulumi didn't bless it, it doesn't exist in Pulumi's world.

That has not been my experience. I have personally ported a Sentry TF provider into Pulumi, and I will grant you that their docs and examples are bordering on active user hatred for exercising the process, but it does work:

https://github.com/pulumi/pulumi-terraform-bridge#adapting-a...

https://github.com/pulumi/pulumi-tf-provider-boilerplate#rea...

What mystifies me about that situation is that I do actually appreciate the amount of silliness that is required to avoid using Pulumi cloud: they are not financially incentivized to make that easy, but I'd guess a lot more folks would nope right out if they didn't make it possible

However, I would think they'd want to make ingesting a TF provider into Pulumi as smooth and reliable as possible, so they don't have people close their browser tab when they don't find a supported provider for Pulumi but it exists in TF