vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
I'm in the process of moving hosts and updating ansible-versions and playbooks.
Due to modules being migrated to galaxy, one of my playbooks has unresolved modules/actions (namely timezone and alternatives).
Running ansible-lint against the playbook also shows the relevant output:
WARNING Listing 1 violation(s) that are fatal
syntax-check[unknown-module]: couldn't resolve module/action 'alternatives'. This often indicates a misspelling, missing collection, or incorrect module path.
common/ubuntu/basic-setup.yml:131:11
Rule Violation Summary
count tag profile rule associated tags
1 syntax-check[unknown-module] min core, unskippable
Failed: 1 failure(s), 0 warning(s) on 1 files.
This, however isn't shown in the Problems-pane of VSCode. It behaves as if there are no errors at all!
Sidenote: After installing the correct module into my collection, ansible-lint inside vscode works as expected.
The Playbook is incorrectly being marked as having no problem, when it couldn't be further from the truth!
ansible-lint --version:
ansible-lint 24.5.0 using ansible-core:2.17.0 ansible-compat:24.5.1 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8
Relevant log output
Path for lint: /root/.local/bin/ansible-lint
Validating using ansible-lint
Path for lint: /root/.local/bin/ansible-lint
Validating using ansible-lint
Path for lint: /root/.local/bin/ansible-lint
Validating using ansible-lint
Summary
I'm in the process of moving hosts and updating ansible-versions and playbooks. Due to modules being migrated to galaxy, one of my playbooks has unresolved modules/actions (namely timezone and alternatives). Running ansible-lint against the playbook also shows the relevant output:
This, however isn't shown in the Problems-pane of VSCode. It behaves as if there are no errors at all!
Sidenote: After installing the correct module into my collection, ansible-lint inside vscode works as expected.
The Playbook is incorrectly being marked as having no problem, when it couldn't be further from the truth!
Extension version
24.5.2
VS Code version
1.89.1
Ansible Version
OS / Environment
Relevant log output