looks like vim-ale has shellcheck built in

ewoud: have fun with puppet-editor-services and using anything but VSCode. I keep running into issues, you have to run the lang server from root of the puppet-editor-services directory or the binaries won't find the ruby files........ BUT most of the editors I like using expect a lang server to be in $PATH, with no easy way to change it. Been fighting with NeoVim/LunarVim and Helix-Editor for a couple

days.

I can get the langserver to start now and nvim to connect, but it still doesn't do any hover docs or autocompletion at all. Just some more errors about not being able to find all the ruby libs

cc bastelfreak binford2k

yeah and I didn't get any feedback for my open issues in a year

@binford2k ^ this is really frustrating. A good UX for developers is needed for the health of the Puppet language, but unlike other tools out there, it seems like the assumption is that all should use VSCode. But even then it still lacks features that most other lang servers have. I'd contribute, but I don't have enough time. It's hard enough to find time to work on

puppet-r10k

and the lack of a good tool is slowing me down a lot

See the

puppet-r10k

module at https://forge.puppet.com/puppet/r10k?src=slack&channel=voxpupuli

even in vscode with the official puppet extension it seems like it's not easily possible to configure different puppet-lint plugins

Failed on puppet:

Failed to connect to puppet: pkeys are immutable on OpenSSL 3.0

meh, my bolt doesn't seem to like openssl 3

https://github.com/puppetlabs/puppet-editor-services/issues/323 looks quite dead :(

Not to mention the current standard for a lot of editors is to use

treesitter

for syntax, but there's no puppet treesitter grammar. Though, to be fair, there doesn't seem to be any treesitter grammars for ansible, chef, or salt either

ansible is YAML and Python, chef is pure Ruby

and I think salt is also YAML + Python

so I'd expect them to not need their own grammar

fair point. Puppet is so drastically different that it does need its own grammar

Salt is jinja -> yaml by default

I.e. you cannot lint it because jinja has no vars defined and yaml is not jinja-processed

oh yes, Ansible also has jinja processing

That means you can only apply to check it for correctness

Ansible is valid yaml with jinja included

Salt is different.. it’s invalid yaml because it’s generated by jinja usually

Seems like the more we try to not make so that SysAdmins don't have to write code, the more code that has to be written to hide the code 😕

I was promised codeless and serverless

and yet here we are in a mess of code and servers

I'd rather teach a sysadmin how to write code, then force them to code to munge data in ansible.

I literally have an ansible block that has a comment above it that's like

# THIS SHIT IS MAGIC, THAR BE DRAGONS HERE, ENTER AT YOUR OWN RISK

jra__, well, noone promised you messless :P