pulumi-terraform-bridge VS pulumi-aws-native

GA: automatic token mapping and aliasing in the bridge, which we're now using to simplify the resources.go file in bridged providers

Yes, pulumi is just wrapping terraform[1]. So you need to understand both the quirks of that and the quirks of pulumi. And I'm lazy so I just want to deal with one quirk at the time.

[1] https://github.com/pulumi/pulumi-terraform-bridge

After digging, I saw python libraries in my venv directory that is related to Terraform Bridge and the tool that was used to generate code - https://github.com/pulumi/pulumi-terraform-bridge

They have an open source tool that translates the TF providers into Pulumi providers, so people could continue to build updated providers - https://github.com/pulumi/pulumi-terraform-bridge

> 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

For provisioning infrastructure in AWS, there are other tools besides those provided by AWS themselves. This includes Terraform and Pulumi. Both of these are not tied to any particular public cloud provider, or not even to public cloud providers only. Any kind of Software-as-a-service (SaaS) provider that can provide some service or infrastructure via programming interfaces can in theory be provisioned by these tools. Terraform has a long list of providers, and Pulumi can use Terraform providers in addition to its providers.

I think they might use their (pulumi-terraform-bridge)[https://github.com/pulumi/pulumi-terraform-bridge] to generate some of their provider code from the corresponding Terraform providers? (This page mentioned some of their "most interesting providers" are created like this)[https://www.pulumi.com/docs/intro/vs/terraform/#using-terraform-providers].

I haven't played with Pulumi in a long while, because we decided that for hiring reasons we'd hold our nose and use the aggressively stupid terraform because at least it's known stupid

But I just fired up a recent version of Pulumi and can say that there is "no long live Pulumi" in its current state because they aped terraform so much it falls prey to the exact same stupidity as terraform, only now featuring their own bugs <https://github.com/pulumi/pulumi-aws-native/issues/108>

  $ pulumi new aws-native-go

Even the pulumi-cdk package is basically not maintaned at all (https://github.com/pulumi/pulumi-cdk). Are there any plans for providing better AWS support? Errors like this here (https://github.com/pulumi/pulumi-aws-native/issues/906) are really frustrating.

>Isn't pulumi aws just terraform under the hood still?

It depends.

The AWS "Classic" provider uses the terraform provider [1].

The AWS "Native" provider does not, and instead uses the AWS Cloud Control API [2].

[1]: https://github.com/pulumi/pulumi-aws

[2]: https://github.com/pulumi/pulumi-aws-native

Isso economiza uma quantidade significativa de tempo e esforço ao eliminar a necessidade de converter manualmente a sintaxe CloudFormation para a sintaxe de linguagem apropriada. Você pode converter Cloud Formation IAC diretamente do site do Pulumi clicando aqui ou usando essa biblioteca.

This saves a significant amount of time and effort by eliminating the need to manually convert CloudFormation syntax to the appropriate language syntax. You can convert Cloud Formation IAC code directly from Pulumi website clicking here or using this official library.

tldr; it wraps Terraform providers poorly and can fail building proper infra diffs from time to time...

https://github.com/pulumi/pulumi-aws-native is nowhere near GA state, just scroll through the issues...

and the respective terraform wrapper https://github.com/pulumi/terraform-provider-aws