Latest News

    • February 6, 2023

      OrchidE 2022.1.3.0

      OrchidE 2022.1.3.0 supports the latest IntelliJ platform EAP version 2023.1 and brings some bug fixes.

      This version of OrchidE is verified against IntelliJ platform version EAP 231.6471.13 from February 3, 2023.


      • Bugfix: Roles Variable files in sub folders are not used in Code Completion and Inspections.
      • Bugfix: When resolving included files with the keyword vars_files, an endless recursion occurs if Jinja variables are used for the file name (StackOverflowException).
      • Bugfix: When resolving Jinja variables with circular dependencies, an overflow occurs during resolution (StackOverflowException).
      • Bugfix: The intention “Add extra variable” is executed already when selecting the entry and not when confirming the entry.
      • Bugfix: Editor tabs show the wrong status for mark modified (*) after saving an Ansible Vault file.
      • Changes: Internal API updates.


      Der Support für die IntelliJ Plattform 2021.2 ist deprecated und endet mit dem Erscheinen der EAP Version der IntelliJ Plattform 2023.2.

    • January 15, 2023

      OrchidE 2022.1.2.0

      OrchidE 2022.1.2.0 comes with more inspections and improvements for imported playbooks.

      A new inspection checks if a used Ansible task without namespace leads to an ambiguity. The listed namespaces in the collections keyword are taken into account.

      Unique Ansible Tasks

      Import playbook

      In playbooks imported from other playbooks (via import_playbook) the keywords ‘vars’ and ‘vars_files’ are now also supported. This means that variables defined with vars/vars_files are used for navigation, code completion and for the inspection ‘Undefined Variables’.

      The feature also supports cascaded imports from playbooks.

      Private role vars

      For navigation, code completion and the inspection “Undefined Variables”, “private role vars” are now also taken into account in Jinja2 templates.

      Private role vars

      Jinja2 templates

      In Jinja2 templates there is now a status bar that displays a breadcrumb of Jinja expressions.

      Breadcrumb in Jinja2 templates


      To have improved support for navigation, quick documentation, code completion and inspections in inventory variable files there is the OrchidE Role Annotation.

      A new intention and inspection support to add the annotation afterwards.

      If the warning for the missing annotation is not desired, it can be configured or disabled in the settings (Settings ➞ Editor ➞ Inspections ➞ Ansible: ‘Missing role annotation’).

      Role annotation inspection & intention


      • Bugfix: Quick fix ‘Create group/host variable’ shows too many possibilities. (Also unsupported meta/argument spec files are shown).
      • Bugfix: Error when a Vault file is opened in the IntelliJ editor and decrypted outside of IntelliJ.
      • Bugfix: Variable values / resolved references of Jinja2 templates are not displayed as inlay in IntelliJ 2022.3.</li>


      Support for IntelliJ platform 2021.1 is deprecated and will end with the release of IntelliJ platform 2023.1.

    • December 5, 2022

      OrchidE 2022.1.1.0

      OrchidE 2022.1.1.0 brings many small improvements and fixes.

      For Ansible Vault files the Vault id can now be set afterwards.

      Set a new vault id

      File references in tasks

      Code assistant functions for the modules include_tasks, import_tasks and template have been improved and extended:

      • File references to Jinja templates now support folders in file path.
      • Navigation to a referenced file is now a single file path (instead of folders + file) entry.
      • Support code completion for sub dictionaries within Jinja templates.
      • Inspection missing file now shows the original file reference string with Jinja templates.
      • New configuration flag to filter code completion suggestions by file extension *.j2 for template task. (Settings ➞ Editor ➞ OrchidE : code completion section).
      • Performance improvements.


      • Change: Inspection undefined variable now finds variables defined with task’s vars keyword.
      • Bugfix: Inlays show wrong values if variable names have the same prefix.
      • Bugfix: Block keyword not detected when followed by a comment.
      • Bugfix: Parser does not recognize the keyword block if it is immediately followed by a comment.
      • Bugfix: Inspection wrong keyword displays an error of an valid name if the name matches a module name.
      • Bugfix: Parser shows an error if a dictionary/list is used in a Jinja function in Jinja templates (e.g. {{ combine(var1, { 'key': value|string + x['abc'] } ) }}.
      • Bugfix: Code completion does not display variables defined with the keyword vars.
      • Bugfix: Inspection wrong module argument type brings an error if referenced values contain a ‘\’ character.


      Support for IntelliJ platform 2021.1 is deprecated and will end with the release of IntelliJ platform 2023.1.

    • October 31, 2022

      OrchidE 2022.1.0.0

      OrchidE 2022.1.0.0 comes with code assistant for Ansible group and host variables in inventories.

      • Code completion of variables based on the argument-spec definition and the defaults file in roles.
        • Optionally, the description is additionally inserted above the variable (code completion with Enter key).
      • Navigation to the declaration of variables in the argument-spec file
      • Quick documentation of the description and meta attributes of a variable (based on argument spec)
      • Type check of variable values based on the definition in the argument-spec file
      • OrchidE own annotation for improved user experience

      Introduction of code assistant for group and host variables

      Code Completion

      (with Role annotation only the matching suggestions are displayed)

      Code completion for group and host variables


      (a role annotation must be present for navigation to work)

      Navigation for group and host variables

      Quick Documentation

      OrchidE supports the HTML shortcuts (e.g. I(italic) for italic) from the Ansible documentation and renders the HTML text correctly when shortcuts are used in the argument spec description.

      Quick documentation for group and host variables

      Type-Check of Values

      Type check for group and host variables


      Folding for group and host variables


      • Change: Binary content in Ansible vault files are detected and no longer displayed in the editor.
      • Bugfix: Error in find usages with unresolved references (IllegalStateException: element.node must not be null).


      Support for IntelliJ platform 2020.3 is deprecated and will end with the release of IntelliJ platform 2022.3.

    • October 4, 2022

      OrchidE 2021.1.8.1

      OrchidE 2021.1.8.1 contains some bugfixes and support for IntelliJ platform version EAP 2022.3.


      • Bugfix: Parser error for Jinja2 expression if using an empty dictionary ('{}').
      • Bugfix: Parser error for Jinja2 expression if using embedded Jinja2 expression
        like {{ lookup('file', '{{ item }}') }}
      • Bugfix: Code completion for Jinja2 braces not working in variable and task files.
      • Bugfix: IDE Error (NPE) during indexing Ansible files within inventory folder.


      Support for IntelliJ platform 2020.3 is deprecated and will end with the release of IntelliJ platform 2022.3.

    • August 8, 2022

      OrchidE 2021.1.8.0

      OrchidE 2021.1.8.0 now supports code completion and navigation go to declaration for template files.

      • Code completion for the src argument of the template module.
      • Navigation to the template file for the module template (without Jinja support)

      For code completion, the default search path is limited to the search path <Ansible search paths>/templates/*.

      In the configuration Editor | OrchidE the behavior can be changed to get all files suggested that Ansible supports.

      Actions for module template

      For variables of type ‘list’ from the argument_spec file, OrchidE now supports code completion for the choices of the list.

      Selection of lists of argument spec options


      • Bugfix: IntelliJ error when a Jinja2 template is selected in the VCS Diff window.
      • Bugfix: Parser error when using concatenated strings in Jinja2 templates, e.g. {{ groups[ + “Server”] }}.


      Support for IntelliJ platform 2020.3 is deprecated and will end with the release of IntelliJ platform 2022.3.

    • July 4, 2022

      OrchidE 2021.1.7.0

      OrchidE 2021.1.7.0 improves the support for variables set with the set_fact module or the keyword register:

      • Code completion for Jinja2 variables now also suggests set_fact/register variables when included via import/include_tasks
      • Navigation to variables set with set_fact/register now also supports variables set in import/include_tasks.
      • The ‘Undefined Variables’ inspection now also supports set_fact/register variables set in imported/included files.

      Sample about variables set by set_fact and register

      The resolution of the imported files takes place hierarchically, thus also (sequence) dependencies of the imported files are recognized.

      The improvements are also available in Jinja2 template files.


      Support for IntelliJ platform 2020.2 is deprecated and will end with the release of IntelliJ platform 2022.2.

      Support for Ansible versions 2.9 and 2.8 is deprecated.

    • May 25, 2022

      OrchidE 2021.1.6.0

      OrchidE 2021.1.6.0 now supports code completion for argument spec variables when used in playbooks and in Jinja2 templates ({{ }}) in roles.

      Code completion for argument spec variables


      • Change: File type patterns for playbooks have been updated to better distinguish between playbooks and variable files.


      Support for IntelliJ platform 2020.2 is deprecated and will end with the release of IntelliJ platform 2022.2

      Support for Ansible versions 2.9 and 2.8 is deprecated.

    • May 2, 2022

      OrchidE 2021.1.5.0

      In OrchidE 2021.1.5.0, the Inspection Undefined Variables detects variables set by the Jinja2 set statement.

      And for the Jinja2 template structures if, for, macro, filter, call there is a check if a corresponding end statement (endif, endfor, …) exists.

      Jinja2 Template with set and control structure function


      • Change: Improved error messages for parser errors.
      • Bugfix: Code completion of module argument doesn’t show arguments with version label.
      • Bugfix: Parser error for expression ‘{%-‘ in Jinja2 templates in Ansible multi-line statements.
      • Bugfix: Error when adding an empty value within the file type pattern dialog.
      • Bugfix: Jinja2 JSON template shows error if Jinja2 template is a placeholder for boolean and number.


      Support for IntelliJ platform 2020.2 is deprecated and will end with the release of IntelliJ platform 2022.2

      Support for Ansible versions 2.9 and 2.8 is deprecated.

    • March 14, 2022

      OrchidE 2021.1.4.0

      OrchidE 2021.1.4.0 now supports navigation to associated files for Ansible files.

      For example, from a role, it is possible to directly navigate

      • to playbooks, which contain the role,
      • to group/host variables,
      • to inventory entries,
      • and to all files within the role.

      The function is available via the IntelliJ action Navigate -> Related Symbol. (Ctrl + Alt + Home, Ctrl + + Up)

      Navigation between Ansible files

      Navigation is supported:

      from playbooks

      • to vars files
      • to roles (-> tasks/main.yml)
      • to group/host variables
      • to inventory entries

      from roles (tasks, vars, defaults)

      • to all files of the role
      • to playbooks, including this role
      • to group/host variables (via included role in playbook)
      • to inventory entries (via included role in playbook)

      from inventory entries (cursor must be on entry)

      • to playbooks
      • to group/host variables

      from group/host variables

      • to playbooks
      • to roles (via playbook)
      • to inventory entries


      Support for IntelliJ platform 2020.1 is deprecated and will end with the release of IntelliJ platform 2022.1

      Support for Ansible versions 2.9 and 2.8 is deprecated.

    • February 14, 2022

      OrchidE 2021.1.3.0

      OrchidE 2021.1.3.0 now supports inventory files in YAML format for the Project View -> Ansible Structure.

      And for inventory group and host entries there is a navigation to playbooks using these groups/hosts and to the corresponding variables.

      The navigation takes place via Navigate -> Related Symbol (Ctrl + Alt + Home, Ctrl + + Up)

      Navigation in inventory files to playbooks / variables


      • Change: The project view ‘Ansible Structure’ now shows the file status in color if the file is under version control.


      Support for IntelliJ platform 2020.1 is deprecated and will end with the release of IntelliJ platform 2022.1

      Support for Ansible versions 2.9 and 2.8 is deprecated.

    • January 14, 2022

      OrchidE 2021.1.2.0

      OrchidE 2021.1.2.0 now assists in creating new Ansible files.

      New file dialog for Ansible files

      The creation is context-independent, i.e. roles are always created in the configured role folder. The New file action uses the facet configuration (facet ‘OrchidE Ansible’) to find the appropriate folder.

      The following types can be created:

      • Roles: creates a folder for the role and depending on the selection an initial file tasks/main.<ext> or meta/main.<ext>.
      • Playbooks: creates a playbook file or folder with a file main.<ext>.
      • Group var: creates an inventory group var file in <inventory>/group_vars folder. Optionally as a folder with default filename.
      • Host var: creates an inventory host var file in <inventory>/host_vars folder.

      If no folder is specified for the type in the facet configuration, the currently selected path from the Project-View is taken as the basis.
      If multiple folders are specified for the type in the facet configuration, the matching path will be searched based on the current path in the Project-View. If the current path is not part of a configured Inventory, Playbook or Role base directory, the current path will be used.

      The default file name for folder-based group var files and the preferred YAML file extension can be configured in the settings (File | Settings | Editor | OrchidE).

      New file dialog for Ansible files


      • Change: Inlay hints can now display recursively resolved values for variables if the reference is unique
      • Change: Inlay hints for Jinja variables now supports set_fact variables.
      • Change: Inlay hints in tooltips now include the path to the file of the reference.
      • Change: Inlay hints can now be displayed as a “tooltip icon”. The complete information is then in the tooltip.
      • Change: Jinja2 templates feature (.j2) now includes support for base template language of YAML files (.yml.j2, *.yaml.j2). (supports combined usage with other yaml based plugins like JetBrains’ Kubernetes plugin)
      • Change: Jinja2 templates feature now adds closing brace for Jinja2 variables template “{{ }}”.
      • Change: The setting for the Ansible version has been replaced by the entry <collections> for version 2.10 and higher. The version is defined by the installed OrchidE builder definition package.
      • Change: The inspections “Deleted Module” has been removed for Ansible version >=2.10. The inspection “Unknown Ansible play, task and block keyword” can be used instead.
      • Bugfix: Inlay hints setting ‘hide default values’ is not working for defaults variables files in roles.
      • Bugfix: Setting file type pattern ‘Task’ was not properly recognized.
      • Bugfix: Introduce Variable refactoring doesn’t work with multi line strings.
      • Bugfix: ‘Comment with Line Comment’ moves cursor one line down in generic Jinja2 template (plain text).


      Support for IntelliJ platform 2020.1 is deprecated and will end with the release of IntelliJ platform 2022.1

      Support for Ansible versions 2.9 and 2.8 is deprecated.
      Support for Ansible version 2.7 has been removed.

    • December 14, 2021

      OrchidE 2021.1.1.0

      OrchidE 2021.1.1.0 can now display the values of Jinja variables as inlay hints.

      Inlay hints for Jinja variables

      Inlay hint of jinja variables

      These inlay hints can be configured in the preferences (File | Settings | Editor | Inlay Hints).


      • Bugfix: Selected editor tab with playbook won’t be selected in Ansible structure tree.
      • Bugfix: Refreshing of Ansible structure view rebuilds tree several times after deleting a file.
      • Bugfix: Resolving of Jinja variables shows wrong entries when name matches part of variable name.


      Support for IntelliJ platform 2020.1 is deprecated and will end with the release of IntelliJ platform 2022.1

    • November 14, 2021

      OrchidE 2021.1.0.0

      OrchidE 2021.1.0.0 comes with a project view for Ansible and a search for inventory entries.

      Project view for Ansible

      Project view

      The project view shows inventory entries and variable files, playbooks and roles and hides the rest of the structure.

      Project view

      Further details can be found in the documentation.

      Support for searching inventory hosts and groups via search dialog

      In the SearchEverywhere dialog it is now possible to search for inventory group and host names and to navigate to the associated declaration or to the associated variable definition. (Shortcut Ctrl+Shift+O, then I, +Shift+O, then I)

      SearchEverywhere in inventory

      Search for and navigation to host and group names is currently available for inventory files in INI format. Also, the INI plugin (ini4idea) from JetBrains must be installed. (YAML for inventory files is not supported).

      For this function, the facet “OrchidE Ansible” must be assigned to a module and configured.


      • Minor bug fixes.


      Support for IntelliJ platform 2019.3 is deprecated and will end with the release of IntelliJ platform 2021.3.

    • October 5, 2021

      OrchidE 2020.1.9.0: Bugfixes and support for newest IntelliJ EAP version

      OrchidE 2020.1.9.0 now supports IntelliJ platform version 2021.3 EAP 2.


      • Bugfix: Inspection “Duplicate Keywords” shows wrong error on role keyword in playbooks.


      Support for IntelliJ platform 2019.3 is deprecated and will end with the release of IntelliJ platform 2021.3.

    • September 6, 2021

      OrchidE 2020.1.8.0: New Features

      OrchidE 2020.1.8.0 allows quick navigation between tasks (via IntelliJ action Next/Previous Method) and easy movement of tasks (via IntelliJ action Move Statement Up/Down).

      Navigation and movement of task

      Navigate to and move of tasks

      Highlighting of Jinja2 statements in multi-line text

      Highlight Jinja2 statements in multiline text

      Structure View window

      The Structure View can now display tasks and includes in playbooks and tasks files.

      Structure view for playbook and tasks


      • Change: Improved deprecated detection of non-FQCN module with same name in different collections.
      • Change: Support jinja2 templates in key names for variables in module set_fact.


      Support for IntelliJ platform 2019.3 is deprecated and will end with the release of IntelliJ platform 2021.3.

    • July 26, 2021

      OrchidE 2020.1.7.0: New Features

      OrchidE 2020.1.7.0 brings a new inspection to check the type of keyword or module argument. Code completion for keywords and module arguments now also offer known values for even faster editing.

      Type Checks

      OrchidE can now check the types

      • boolean,
      • integer and
      • selection list

      for keywords and module arguments and warn when type is wrong.

      The use of Jinja variables with simple references is also supported.

      Type definitions are used from collection and keyword documentation. Custom definitions from argument_specs are currently not supported.

      Type check

      Code Completion with values

      Boolean and selection lists are now included as additional code completion suggestion at keywords and module arguments.

      Code completion with values

      Which combination of boolean (true/false, yes/no, on/off) is suggested can be set in the editor settings.


      • Change: Support code completion for variables for debug: -> var:.
      • Change: Various improvements and fixes for include_tasks in code completion and navigation “go to declaration”.
      • Bugfix: Inspection undefined variables does not consider loop variable in Jinja templates from host/group variables.
      • Bugfix: Error displaying “no valid file” for arguments with name “file”.


      Support for IntelliJ platform 2019.2 is deprecated and will end with the release of IntelliJ platform 2021.2.

    • June 22, 2021

      OrchidE 2020.1.6.0: New Features

      OrchidE 2020.1.6.0 comes with improvements for Ansible include-modules (import_tasks, include_tasks, import_playbook und vars_files).

      OrchidE now additionally supports

      • code completion for files to include
      • navigation support for full path
      • inspection for missing files
      • the creation of missing files
      • the creation of additional files when Ansible Facts variables are used

      At least IntelliJ Platform 2019.3 is required to create new files (for Ansible fact based insertion).

      Create file intention

      Supported Ansible facts are

      • ansible_distribution
      • ansible_os_family
      • ansible_system
      • ansible_distribution_major_version

      More facts available via email or via GitHub issue/pull request for the definition file.


      • Change: inspection undefined variables now also recognizes variables in loops with with_dict.
      • Change: new inspection to detect duplicate YAML keys.
      • Bugfix: error when setting a variables file to plain text.
      • Bugfix: parser error in string concatenation in Jinja2 templates.
      • Bugfix: missing html entity decoding in documentation of return values.


      Support for IntelliJ platform 2019.2 is deprecated and will end with the release of IntelliJ platform 2021.2.

    • May 15, 2021

      OrchidE 2020.1.5.0: New Features

      Orchid 2020.1.5.0 now has code completion and navigation support for the Ansible keywords. when, failed_when, changed_when and until.

      For variables defined by the keyword register, code completion, navigation and quick documentation are now supported. These functions are supported for variables defined within the same file.

      Support for when condition and register

      • Code completion support for Ansible variables in conditions
      • Go to declaration for Ansible variables used in conditions
      • Code completion support for register variables, including code completion of return-values.
      • Go to declaration of register variables.
      • When using register variables, the documentation of return values will be shown in the quick documentation.

      Jinja2 Templates

      The inspection undefined variables now detects loop variables in Jinja2 templates.

      Inspection undefined variables supports Jinja2 template loops


      Support for Ansible 2.11 and improved setting dialog for configuring collections.

      • Configuration of collections via keyboard.
      • Reloading the collection configuration after applying the changes without restarting.

      Module set_fact

      Code completion and go to declaration support for variables set by module set_fact (within the same file).


      • Change: Stability improvements when working with multiple projects.
      • Change: Note on recommended configuration setting for OrchidE extension and use of Ansible 3.3.
      • Change: Removed support for Ansible 2.6 and 2.5.
      • Bugfix: Fixed missing arguments, removed wrong arguments from command modules (shell, command, script, …) (Ansible 2.8, 2.9).</li>


      Support for IntelliJ platform 2019.2 is deprecated and will end with the release of IntelliJ platform 2021.2.

    • April 14, 2021

      OrchidE 2020.1.4.0: Support for Ansible vault files

      OrchidE 2020.1.4.0 can now decrypt and encrypt Ansible vault files.


      (Update Apr. 16, 2021)

      This version is now available on the Marketplace.

      This version is currently not available via the JetBrains Marketplace.

      Please download the version from the website and install the plugin via the plugin settings (Icon für Install –> “Install Plugin from disk “)

      • OrchidE 2020.1.4.0 für IntelliJ Version >= 2019.3.1
      • OrchidE 2020.1.4.0 für IntelliJ Version 2019.2
      • OrchidE 2020.1.4.0 für IntelliJ Version 2019.1

      The usual download from the Marketplace will be delivered as soon as possible.

      • Decrypt Vault files with and without Vault id.
      • Decrypted files can be used like normal files with variables - supports navigation, code completion, inspection
      • Optional persistent storage of the password in the IntelliJ password safe for each Vault id. Alternatively, the password is only kept in memory.
      • Encrypt new files with/without Vault id.
      • Support for IntelliJ’s “Auto-Save” feature - OrchidE encrypts Vault files when IntelliJ saves them. Passwords (within Ansible files) are never stored in plain text - even if they are visible in the editor.
        Explicit encryption is not necessary.
      • Supports comparison of Vault files with VCS.

        Support for Ansible Vault files

      More details about decrypting/encrypting can be found in the documentation.


      • Change: Further performance improvement for the inspection “Undefined Variables”.
      • Change: Inspection “Undefined Variables” now also supports variables defined in include-/import_role
          - import_role:
              name: test_role
              testkey: "hello" 

      Restrictions for IntelliJ platform 2019.1 and 2019.2

      If there is more than one open project with IntelliJ platform versions 2019.1 and 2019.2, the “Close Project” button must be pressed twice, if there are unsaved vault files.


      Support for IntelliJ platform 2019.2 is deprecated and will end with the release of IntelliJ platform 2021.2.

      OrchidE version 2020.1.4.0 is the last version supporting IntelliJ platform 2019.1.

    • April 10, 2021

      Announcement: Delay in the publication of OrchidE releases

      Due to a re-organization for the development of OrchidE, unfortunately no releases can be published at the moment.

      We are working to complete the re-organization as soon as possible and release new releases.

    • December 15, 2020

      OrchidE 2020.1.3.0: Performance improvements and new features


      OrchidE 2020.1.3.0 includes performance improvements for navigation and Inspection Undefined Variables.

      Code completion

      Code completion is now available for Ansible module arguments that expect a value from a choice.

      Code completion for module arguments

      Code completion, navigation und inspection “undefined variables”

      Code completion, goto declaration and a validation by inspection “undefined variables” are now available for further variable definitions:

      • for variables defined in playbooks with the keyword vars are now fully supported in role tasks.
      • for variables defined in playbooks -> roles: -> vars: are now fully supported in role tasks.


      • Changes: added documentation for Ansible keywords (requires OrchidE-Builder update -> (Settings | Languages & Frameworks | Orchide | Extension)

        Quick documentation for keywords

      • Bugfix: Fix IllegalStateException if code completion for Ansible is set to version 2.9 or lower.


      Support for IntelliJ platform 2019.1 is deprecated and will end with the release of IntelliJ platform 2021.1.

    • November 16, 2020

      OrchidE 2020.1.2.0: Configuration Options for Code Completion of Collections

      In version 2020.1.2.0 you can configure code completion for collections. You can choose between

      • use only the full qualified collection name (FQCN)
      • use only the short name (module name)
      • use the short name based on the keyword collections. If collection is not listed, the FQCN and short name will be displayed
      • always show FQCN and short name

      Settings for code completion of collections


      For the module include_tasks file names with Jinja2 templates are now supported.

      Sample navigation to dynamic include tasks

      This function requires the OrchidE-Builder extension (File | Settings | Languages & Frameworks | OrchidE | Extension) and is only supported for a selection of variables.

      Missing variables can be requested via email or Github Issues.

      More details can be found in the documentation


      The assignment of the file extension for YAML is no longer mandatory for OrchidE. OrchidE can now also YAML files recognize if the extensions *.yml, *.yaml are assigned to the YAML plugin.

      This allows the parallel use of OrchidE with other YAML-based plugins and improves the detection of ansible files after IntelliJ updates.


      Support for the IntelliJ platform 2019.1 is deprecated and ends with the release of the IntelliJ platform 2021.1.

      IntelliJ IDEA EAP 2020.3 support

      OrchidE now supports IntelliJ IDEA EAP 2020.3.

      OrchidE needs the YAML Plugin or a manual assignment of the file extension to recognize the YAML files

      At the time of release of new EAP versions it may happen that there is no YAML plugin in the JetBrains plugin repository. A current snapshot build for manual installation is usually available in the Snapshot Repository.

      Alternatively you can set the assignment of the file extension in the settings (File | Settings | Editor | File Types).

    • October 12, 2020

      OrchidE 2020.1.1.0: Quick Documentation Support for Ansible Modules

      In version 2020.1.1.0 OrchidE supports the display of the documentation for Ansible modules.

      Quick documentation support

      The IntelliJ Quick Documentation Popup and Tool Window now displays documentation on ansible modules and arguments.

      OrchidE shows the description of modules and their arguments. Included is the description, the requirements and notes, the documentation on arguments, return values and examples.

      The documentation is not part of the plugin and must be installed after the installation/update of the OrchidE plugin.

      To install the documentation, open the dialog File | Settings | Languages & Frameworks | OrchidE | Extension, set the download directory and download the OrchidE Definition Archive. After that a restart of IntelliJ is necessary.

      Configuration dialog OrchidE extension


      • Bugfix: Fixed the parser error when using “/” in calculations within Jinja2 templates.
    • August 29, 2020

      Special Anniversary Price

      50% discount for private use and 30% for organizations

      sample discount code

      see details

    • August 24, 2020

      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.
    • June 29, 2020

      OrchidE 2019.1.12.0: Fixes in the parser


      • Change: Improved block support.
      • Change: Parser improvements for YAML flow sequences.
      • Change: Updates for support of IntelliJ platform 2020.2.
      • Bugfix: Support “,” after last element in flow sequence.
    • May 28, 2020

      OrchidE 2019.1.11.0: Fixes in the parser


      • Change: Improvements of the parser when interpreting plain scalar texts.
      • Bugfix: Fixed parser error when using text in quotation marks within Jinja2 templates.
      • Bugfix: Support for role names with special characters for the command Go to Declaration.
      • Bugfix: Incorrect recognition of TODOs in role and variables files.
    • April 29, 2020

      OrchidE 2019.1.10.0: Supports the creation of Ansible variables based on Jinja2 templates

      In version 2019.1.10.0, you can create Ansible variables for roles and host/group vars directly from Jinja2 template code.

      Intention to create Ansible variable

      With the intentions “Create vars variable” and “Create defaults variable” it is possible to create Ansible variables directly from Jinja2 template code ({{ my_variable }})

      With the intention “Create host/group var variable” a variable can be created for each Ansible Reference in an existing host/group var based on a Jinja2 template code.

      To use Ansible command line variables (parameter –extra-vars) in OrchidE, such variables can be created in OrchidE. These variables will taken into account durtaing code completion and the inspection “Undefined Variable”.

      Settings Extra Vars

      These variables are stored in the IntelliJ .idea project directory (orchide-extravars.xml) and can checked-in to version control system.

      With the Quick Fix action for the inspection “Undefined Variable” new variables can easily be added to the list. Quick Fix extra vars

      Other changes

      • Bugfix: Fix error on enter in empty file
      • Bugfix: Fix parser error in multi line strings when using multi line quote strings
      • Bugfix: Fix several parser errors in jinja strings
      • Bugfix: Fix error when using a module name string as jinja reference
      • Bugfix: Fix quick fix error in plain text jinja templates
    • March 25, 2020

      OrchidE 2019.1.9.0: Changes, bug fixes and support for custom directory layout for Ansible files

      In version 2019.1.9.0, pattern matching can now be configured to detect Ansible playbooks, roles and variables. This means that any folder structure can now be used with OrchidE and roles and playbooks can be created in any parent folder.

      Settings for detection of Ansible files

      Folding now supports more elements - playbooks, keywords, tasks, modules, module arguments, blocks, multi-line text, lists and dictionaries are now supported.

      To fully expand and collapse all elements, you must activate the folding in the settings. (File | Settings | Editor | OrchidE | Section Folding)

      The default setting still only considers tasks and top-level variables.

      Folding settings dialog

      Other changes

      • Change: when inserting modules with “free_from” argument via code completion, no line break is inserted anymore (shell, command, import_tasks, …)
      • Change: support tag !unsafe for raw strings
      • Change: improvements and fixes for indent on enter feature
      • Bugfix: fixes various parser errors for Ansible filter
    • February 24, 2020

      OrchidE 2019.1.8.0: Changes, bug fixes and support for IntelliJ EAP 2020

      Version 2019.1.8.0 now indents the cursor automatically and supports the EAP program 2020.1.

      Enter now automatically indents based on typical usage in Ansible Playbooks and Roles. For the keywords - block, rescue, always, tasks, pre_tasks, post_tasks and handlers - the hyphen for the typically following tasks are added.

      To unindent a line, the “Smart Key” setting Unindent on Backspace is supported. Note: In OrchidE there is no distinction between the two indent options of IntelliJ.

      Furthermore, the indentation can be undone by pressing the “Enter” key if the current line is a blank line. This functionality is deactivated by default and must be activated via Settings -> Editor -> OrchidE.

      It is now possible to use encrypted values for variables in playbooks, roles and vars files (YAML tag !vault)

      Other changes

      • Change: variable name can now begin with “_” or numbers
      • Change: (internal) plugin metadata changed to organization id
      • Change: improvement of the parser for multi line text.
      • Bugfix: fixes the parser error when a comma comes after a jinja variable.
      • Bugfix: fixes the parser error when using lists below roles:.
      • Bugfix: fixes code-completion in the handler: section in playbooks.
    • January 28, 2020

      OrchidE 2019.1.7.0: minor changes and bug fixes

      Version 2019.1.7.0 of OrchidE now ignores Ansible vault files and supports the keyword vars in tasks.

      • Change: support keyword vars within tasks. Variables defined by vars keyword are used by code completion, inspection undefined variables and navigation go to declaration. Fixes also the navigation bug of playbook keyword vars.
      • Change: support detection of Ansible vault files. OrchidE no longer parses and inspect Ansible vault files. Ansible vault files will now be opened as plain text.
      • Change: support latest JetBrains Floating License Server API.
      • Bugfix: fix wrong deprecated warning when switching from configured Ansible 2.9 to an older version.
      • Bugfix: fix inspection deleted modules showing wrong result when switching from configured Ansible 2.9 to an older version.
      • Bugfix: parser trim support for yaml multi line text (|-, >-).
      • Bugfix: NPE com.taff.plugin.orchide.codeinsight.OrchideUtilKt.getType.
      • Bugfix: fix TypeCastException when triggering code completion within empty blocks.
    • November 28, 2019

      OrchidE 2019.1.6.0: IntelliJ platform 2019.3 support

      Version 2019.1.6 of OrchidE now supports IntelliJ platform 2019.3.

      Playbooks now supporting the keyword vars: for code completion and the inspection “Undefined Variables”.

      • Bugfix: missing keywords “become_exe” and “throttle” of Ansible 2.9 added.
      • Bugfix: fix commenter exception “Access is allowed from event dispatch thread only.”
    • November 4, 2019

      OrchidE 2019.1.5.0: Ansible 2.9 Support

      Version 2019.1.5 of OrchidE now supports Ansible version 2.9.

      A new inspection “Removed Modules” now helps migrating to a new Ansible version. Starting with Ansible Version 2.9 removed modules are still accepted by the parser, but can be declared as a warning or error via the inspection “Removed Modules” and can be reviewed in the inspection results. Inspection Deleted Modules for Ansible 2.9

      • Change: the inspection for detecting Deprecated Modules now shows the names of the module and possibly existing replacement modules.
      • Bugfix: Jinja2 Whitespace Control - Jinja2 templates will now be correctly parsed when using Jinja2 Whitespace Control expressions {{-, -}}.
      • Deprecated: support for Ansible Version 2.5 syntax highlighting and code completion is deprecated.
    • September 30, 2019

      OrchidE 2019.1.4.0: minor changes and bug fixes

      Version 2019.1.4.0 of OrchidE now also allows “yaml” as file extension and brings some bugfixes.

      • Change: it is now also possible to use the file extension yaml for Ansible files.
      • Bugfix: when extracting selected text into a Jinja variable, too much text was cut if the cursor was at the end of the line.
      • Bugfix: fixed the StringIndexOutOfBoundsException in the Jinja2 template parser.
      • Bugfix: for Jinja variables the refactoring menu is now hidden (“Extract Variable/Constant”).
      • Bugfix: fixed performance problem when opening the context menu in the editor and the refactor menu.
      • Bugfix: fixed detection of group/host variable files with standard directory layout.
    • August 29, 2019

      OrchidE 2019.1.3.0 brings Jinja2 template support

      Jinja2 templates

      OrchidE now supports Jinja2 templates.

      Jinja2 template support for Ansible templates

      OrchidE supports Jinja2 templates for

      • XML (“.xml.j2”)
      • JSON (“.json.j2”)
      • Properties (“.properties.j2”)

      Files. Other file extensions are interpreted as plain text. To use the Jinja2 template support, the file extension “.j2” must be appended.

      In Jinja2 expressions ({{ }} / Ansible variables and filters) and simple statements ({% % %}) are supported. Also all IntelliJ functions are supported as for Ansible playbooks and roles (Goto functions, search, highlighting, code completion).

      Inspection undefined variables with improved loop support

      The inspection undefined variables can now check dictionaries in loop variables.

      Quick fix support for undefined variables in loops


      • The goto function (for Goto Ansible variables - Navigate | Symbol, Ctrl + Alt + Shift + N, Cmd + Alt + O) now searches inside all roles of the project.
        So far, the search has been limited to host and group variables and other variables depending on the active editor.


      • OrchidE now also recognizes YAML files as Ansible variables file which are stored directly in the folder group_vars.
      • The goto function (Navigate | Class, Ctrl + N, Cmd + O) now finds role files in role folders with the pattern “roles[^/]*”.
        So far, the pattern has been “roles\/”.
    • July 25, 2019

      OrchidE 2019.1.2.0 released

      OrchidE now supports the IntelliJ platform version 2019.2. Shortly after JetBrains has released its latest version, you can already use OrchidE with it.


      • Code Completion for Jinja variables now also shows snippets of values. Code completion of Ansible variables with display of values
      • Code Completion for Jinja variables now also works with incomplete Jinja templates and subsequent parser errors. Code completion with open Jinja brackets


      • Comments directly after a multi-line string are now correctly displayed as comments.
      • Keywords that were only added with an Ansible Version 2.5 - 2.8 are now correctly compared with the set version and are is correctly hidden and shown during code completion.
      • The goto function (Navigate | Class, Ctrl + N, Cmd + O) now also finds playbook files without explicit subfolders.
      • Code Completion for block keywords now also works for always and rescue.
    • July 12, 2019

      The latest version of OrchidE now supports more IntelliJ products and syntax highlighting and code completion for Ansible version 2.8.

      • OrchidE now supports code completion and syntax highlighting for the latest Ansible version 2.8.
      • OrchidE can now be used with more JetBrains products, it’s now compatible with
      • DataGrip
      • GoLand
      • PyCharm
      • PhpStorm
      • RubyMine
      • WebStorm

      to use OrchidE, at least version 2019.1.1 of the respective JetBrains product is required