molecule VS vscode-ansible

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 :)

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 ↗