vscode-ansible VS ansible-lint

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 ↗

Ansible-lint version 6.14.6 is here, started using ruff linter along with 10+ bugfixes in this release.

Ansible-Devtools team made a new release of Ansible-Lint version 6.14.2 with couple of exciting bugfixes.

The Devtools team has released ansible-lint version 6.14.0, which includes 23 bugfixes and 3 minor changes. Please refer to the changelog here for more information.

ansible-lint 6.14 was released, dropping support for py38 and including over 25 changes and bugfixes.

Ansible-lint 6.13 introduces a new feature that allows users to utilize a .ansible-lint-ignore file. This file contains skip-rules that are loaded from the ignore file which is adjacent to the config file. Additionally, users can take advantage of the --generate-ignore argument to dump any current violations into an ignore file.

Cool, but ansible-lint and the official RedHat docs are a much better way to ensure you're using the official best practices. No offense, but stuff two random guys on Reddit threw together isn't a great resource for best practices.

Check https://github.com/ansible/ansible-lint/discussions/2534 for details and comment there if you detect any regressions.

There is more context here: https://github.com/ansible/ansible-lint/issues/578

ansible-lint 6.4.0 was released with lots of bugfixes and a new feature called "profiles", one that allow you to easily pick which set of rules you want to follow. https://github.com/ansible/ansible-lint/discussions/2254

I use vanilla vim or nvim with checks from ansible-lint.