pulumi-tf-provider-boilerplate
aws-cloudformation-resource-providers-rds
| pulumi-tf-provider-boilerplate | aws-cloudformation-resource-providers-rds | |
|---|---|---|
| 3 | 1 | |
| 68 | 25 | |
| - | - | |
| 5.2 | 8.2 | |
| 12 days ago | 1 day ago | |
| Go | Java | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pulumi-tf-provider-boilerplate
-
We are the Pulumi Engineering team - Ask us about our new products and features
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.
-
What's missing in Pulumi?
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.
-
Terraform 1.0 Release
> 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
aws-cloudformation-resource-providers-rds
-
Terraform 1.0 Release
Merely as the technical answer to your question, not as advocacy: CFN has custom providers [0] and they've started publishing quite a few implementations on GH (but I haven't tried them to know if they're for real): e.g. https://github.com/aws-cloudformation/aws-cloudformation-res...
As far as I know, it is possible to bridge terraform providers into a CFN stack using that mechanism, similar to how Pulumi works
0: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
What are some alternatives?
civo-production-ready-kubernetes - The repository for the CIVO Navigate talk: How To Build A Production Ready Kubernetes
cue - CUE has moved to https://github.com/cue-lang/cue
pulumi-aws-native - AWS Native Provider for Pulumi
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
terraform-lsp - Language Server Protocol for Terraform
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
cnab-spec - Cloud Native Application Bundle Specification
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
terraform-ls - Terraform Language Server
pulumi-provider-boilerplat
mazzle-starter - infrastructure built using devops-pipeline
magic-modules - Add Google Cloud Platform support to Terraform