pulumi-aws-native VS pulumi-aws

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

Sure, but the providers for some of the biggest platforms are maintained by HashiCorp[1] - like the AWS, Azure, GCP, and Kubernetes providers[2], and it appears the Pulumi AWS provider (for example) _does_ use the Terraform AWS provider, even to this day[3].

1. https://developer.hashicorp.com/terraform/registry/providers... - "official" providers are maintained by HashiCorp

2. https://registry.terraform.io/browse/providers?tier=official - The filtered list of "official" providers maintained by HashiCorp

3. https://github.com/pulumi/pulumi-aws/tree/008c4360bc9fc24303... - Just prove it to myself, I can see the `upstream` git submodule, which embeds pulumi/terraform-provider-aws, which is a fork of hashicorp/terraform-provider-aws, although the repo was not created as a fork in Github, so it is not marked as a "fork" and so I have to compare commit histories to tell that it is a fork.

>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

Pulumi uses terraform providers to schematize the CRUD options for some cloud providers. Part of the difficulty with any infrastructure as code offering is that your favourite cloud provider doesn't always provide a full API spec, so we need to somehow figure out what resources can be created, what parameters are available to those resources etc. We take the terraform provider, look at the available operations for that provider and then turned it into a Pulumi schema, which can then be read by the Pulumi engine. If you take a look here you can actually see that generated schema for AWS.