-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestions show all installed collections as part of 'ansible.builtin' #1164
Comments
I have had success with this from a alternate workstation connecting to a different remote host, so it would seem that this is something messed up either with my primary workstation or the language server on the remote host (or both). |
I have the same problem. All suggestions are in ansible.builtin.* although ansible-lint reports that the canonical name should be used, e.g. community.general.*. I recently had to reinstall Ansible via brew, so maybe something broke during that process? Operating System Ansible (installed via brew install ansible)
Ansible Collections
|
Summary
I am experiencing an issue where only modules in 'ansible.builtin' namespace are recognized correctly or suggested. Additionally, any collections (community.vmware, community.general etc) are listed in suggestions as belonging in the 'ansible.builtin' namespace (see screen capture below). I've reinstalled the extensions, reinstalled vscode and deleted the .vscode* files and directories on the remote Linux host in an effort to let it set itself back up. I've also removed/reinstalled ansible-core, ansible-lint, the ansible collections etc all to no success.
I've checked to ensure that collections etc.. are all installed in the expected location ~/.ansible/. If I remove collections the modules still appear as suggestions (still in the incorrect name-space).
Extension version
2.13.148
VS Code version
1.87.2
Ansible Version
OS / Environment
Running VS code on windows 10, using Remote Development SSH to RHEL8.9 server.
$ ansible-lint --version
ansible-lint 6.14.3 using ansible 2.15.9
A new release of ansible-lint is available: 6.14.3 → 24.2.1
Relevant log output
The text was updated successfully, but these errors were encountered: