pulumi-terraform-bridge
vim-lsp
Our great sponsors
pulumi-terraform-bridge | vim-lsp | |
---|---|---|
7 | 81 | |
180 | 3,017 | |
5.0% | - | |
9.7 | 6.4 | |
4 days ago | 4 days ago | |
Go | Vim Script | |
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-terraform-bridge
-
We are the Pulumi Engineering team - Ask us about our new products and features
GA: automatic token mapping and aliasing in the bridge, which we're now using to simplify the resources.go file in bridged providers
-
Converting Full Terraform Programs to Pulumi
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
-
Weird warning after running pulumi preview
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
-
CDKTF
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
-
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
-
Is AWS Cloud Development Kit (CDK) right for you?
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.
-
For IaC: Pulumi or Terraform?
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].
vim-lsp
-
Using SonarLint language server in Vim?
Has anybody managed or got an idea how to make SonarLint Language Server work with e.g. vim-lsp?
-
Vim Golang syntax is ugly
You need to configure a language server. For C++ it's a bit tricky, so good luck with Go. There are other plugins that provide semantic highlighting using LSP, for example https://github.com/prabirshrestha/vim-lsp (I didn't try it, but it seems good).
-
Vim-writegood: nothing, but a simple Vim9 wrapper around write-good.
ALE can use LSP as well. And if you are using vim-lsp, you can use the same instance of server for both with vim-lsp-ale bridge plugin.
-
small vimrc and lsp?
I feel the same way. Not a one-liner but the smallest config LSP plugin I've found is vim-lsp. It works in both Vim and Neovim.
-
Should I move to NeoVim?
The only major feature that Neovim still has is a built in LSP client. But I find the built in Neovim LSP client is unusably buggy, you're much better off using any of the other LSP plugins. What I use is vim-lsp, but I've tried all of the major lsp client, they are all significantly better than the built in Neovim LSP.
- Starting with linux, my experience
- Does vim have a built in/plugin version of vscode's command click?
-
install lsp in vim
As for install/configuration, all you need is the latest Vim, the plugins I mentioned, and that bit in your vimrc. You can do a bit better than that if you copy the entire config with mappings from the vim-lsp GitHub page.
-
How to improve deoplete and vim-lsp (pylsp /jedi-language-server)
I have a problem with Deoplete and Vim-LSP completion (Python's Pylsp and Jedi-Language-Server). The suggestion is much less, and it also misses a lot of opportunities to suggest compared to Deoplete-Jedi, which literally defeats the former by a large margin. Is there a setting to make this duo works like deoplete with deoplete-jedi?
-
The Ruff python linter is insanely good
- add the [prabirshrestha/vim-lsp](https://github.com/prabirshrestha/vim-lsp) plugin and config to your `.vimrc` (note: `pylsp` is *not* necessary).
What are some alternatives?
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
terraform-ls - Terraform Language Server
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
YouCompleteMe - A code-completion engine for Vim
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
terraform-provider-spacelift - Terraform provider to interact with Spacelift
vim-lsc - A vim plugin for communicating with a language server
aws-cloudformation-res
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.