molecule VS ansible-language-server

Hell, the ansible roles I maintain use Molecule for testing.

The Ansible team announced at AnsibleFest and Ansible Community Days last month that Molecule will be released as a developer preview on its way to being a fully supported part of the Ansible platform. In order to achieve this, Molecule will need to be streamlined and refocused as a test runner for functional testing of Ansible playbooks and roles using Ansible itself. This will require a number of breaking changes to happen before releasing “Molecule 6” in order to do all of this. You can read about the changes here and we welcome your questions and feedback on their roll out: https://github.com/ansible-community/molecule/milestone/35

I would recommend you to use roles instead of just playbooks and to test them with molecule. Molecule allows you to quickly test your Ansible roles in a fresh Arch Linux podman container, completely isolated from your real system.

Please post comments on https://github.com/ansible-community/molecule/discussions/3555

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

I’m assuming you are using Molecule: https://github.com/ansible-community/molecule

Please upvote your prefered answer from the https://github.com/ansible-community/molecule/discussions/3130 survey which proposed joining ansible-lint and ansible-molecule channels when we move them from freenode irc to libera.chat. There is also an option to keep the channels separated.

Just as a heads up, Molecule has a very active discussion area on GitHub.

Ansible Molecule

But to be fair, a lot has changed since 2017 :)

Version 1.1.0 The Ansible Language Server (ALS) underwent a substantial upgrade. ALS v1.1.0 has adopted the new YAML 2.x package and successfully updated its code base accordingly. This significant development brings enhanced capabilities in terms of YAML diagnostics and strengthened security measures. Another crucial feature addition was the completion for variables declared inside a playbook. Full list of change-logs here.

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :

You are conflating multiple functions. I have used the ansible language server 1 with decent success in both 0.7 and 0.8. It provides autocompletion of modules and diagnostics from ansible-lint, but does nothing to address syntax highlighting. Your project should have either an ansible.cfg or .ansible-lint at your project’s top level and your yaml files should be of filetype yaml.ansible. If you run :LspInfo it should display ansiblels as active.

I'm looking to use a language (Ansible flavored YAML) that does have an LSP implementation, but is not supported by tree-sitter.

Does the standalone usage help?

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

Additionally, I found that the entire extension stopped working because in the past, easy-install had added a .egg file to my python path. I submitted a fix and it was accepted, but I'm not sure if the fixed language server is part of the current extension version. Might be worth checking for files like that in the paths listed in sys.path.

I think we found the bug as https://github.com/ansible/ansible-language-server/issues/117