vscode-ansible VS ansible-language-server

The place to open issues for the plugin https://github.com/ansible/vscode-ansible

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

Ansible-VSCode extension 2.0.0 is out!

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 :

I asked the devtools team and here is their reply: "The telemetry data is sent to the Red Servers and are not publicly available. Though we have documented the usage data that we gather here."

Best place to read the changelog is at https://github.com/ansible/vscode-ansible/releases but marketplace only links to the embedded changelog file, which is not as good as the github releases page (hyperlinks,...)

Ansible extension for vscode/codium

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

For example one recent bug we found is that defining ANSIBLE_FORCE_COLOR=1 can prevent the extension from working. I do expect that a number of ansible users to configure that in env or in their ansible.cfg file,... Details https://github.com/ansible/vscode-ansible/issues/373 -- we plan to release a fix later this week for this one.

DevTools ↗

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