OrchidE Version 2020.1.0.0: Ansible Galaxy Collection Support

OrchidE 2020.1.0.0: Support for Ansible Galaxy Collections

In version 2020.1.0.0 Ansible Collections are now supported and it is possible to navigate to target files for import/include modules.

Ansible Collection support

OrchidE now supports modules of the most common Ansible Galaxy Collections - in FQCN and short notation. The support includes parsing of Ansible files and the code completion for modules for Ansible version 2.10.

Ansible collection support in OrchidE

OrchidE can be extended with additional Ansible Collections to add missing or updated collections. For this purpose there is a CLI tool on GitHub to create updated definitions.

For the modules (and arguments)

  • import_playbook
  • import_tasks
  • include_tasks
  • include_tasks: -> file:
  • import_role: -> name:
  • include_role: -> name:
  • include_vars: -> file:
  • vars_files:

the navigation “Go to Declaration” (Ctrl + B/Command + B) is now supported. Supported are file/path names relative to the current file.

New inspections

New Inspections check the validity of keywords and module arguments:

  • Inspection “Unknown Ansible play, task and block keyword”
  • Inspection “Unknown Ansible role keyword”
  • Inspection “Unknown module argument”

(Supported for Ansible versions 2.8 - 2.10)

OrchidE Inspection Unknown Keyword and Argument

Open issues

When using modules in short form there are restrictions if two or more collections use the same name (e.g. user)

In this case, all module arguments are always offered by code completion. Also, the inspection “Unknown module argument” checks for all arguments of all possible modules.

The Inspection “Removed Modules” is not yet adapted to version 2.10 of the Ansible project.


  • Bugfix: Fixed wrong highlighting for non-playbook/tasks files.