pulumi-tf-provider-boilerplate
terraform-lsp
| pulumi-tf-provider-boilerplate | terraform-lsp | |
|---|---|---|
| 3 | 5 | |
| 68 | 572 | |
| - | - | |
| 5.2 | 0.0 | |
| 12 days ago | about 1 year ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
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
terraform-lsp
- Help with implementing missing LSP functionality in Terraform
-
Workflow for DevOps? (Ansible, Terraform, Kubernets, RHET)
Look at terraform-ls vs terraform-lsp. Both can be used with coc.nvim.
- Terraform 1.0 Release
-
How to set terraform language pack in spacemacs?
Also installed terraform-lsp as its steps.
-
Using terraform-ls with Kate as LSP Client
Also try terraform-lsp and see if it works.
What are some alternatives?
civo-production-ready-kubernetes - The repository for the CIVO Navigate talk: How To Build A Production Ready Kubernetes
terraform-ls - Terraform Language Server
aws-cloudformation-resource-providers-rds - The CloudFormation Resource Provider Package For Amazon Relational Database Service
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
pulumi-aws-native - AWS Native Provider for Pulumi
cue - CUE has moved to https://github.com/cue-lang/cue
cnab-spec - Cloud Native Application Bundle Specification
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
dhall-kubernetes - Typecheck, template and modularize your Kubernetes definitions with Dhall
mazzle-starter - infrastructure built using devops-pipeline
aws-cloudformation-res