OrchidE 2025.1.4.1 adds support for the EAP 2026.3 program and includes bug fixes.

Changes

• Change: Add support for code completion of ansible_facts for the debug task.
• Bugfix: Related Items action does not resolve host and group vars via inventory groups when using INI files for inventory.
• Bugfix: Quick fix to suppress undefined variable doesn’t insert suppression on conditional keywords like when, until,…

Deprecation

• Support for IntelliJ platform 2024.3 is deprecated and will end with the launch of the EAP for IntelliJ platform 2026.3.

OrchidE 2025.1.4 now supports Ansible Magic Variables and access to Ansible facts through the ansible_facts array.

Code Completion is available for both. Quick Documentation is also supported for Magic Variables. Deprecated variables with the ansible_ prefix can be refactored across the entire project using the quick fix provided by the “Deprecated usage of injected facts” inspection.

Ansible facts array

OrchidE provides Code Completion for Ansible facts accessed through the ansible_facts array, for example ansible_facts["os_family"].

Code Completion is also available within the array.

The OrchidE inspection “Deprecated usage of injected facts” warns when Ansible facts are still accessed through deprecated injected variables with the ansible_ prefix.

The quick fix can replace all injected Ansible facts across the entire project with the array notation ansible_facts["<fact name>"].

The format in which Ansible facts are suggested by Code Completion can be specified under Settings ➞ Editor ➞ OrchidE: Code Completion.

Magic Variables

OrchidE now also supports Code Completion and Quick Documentation for Ansible Magic Variables.

Changes

• Bugfix: Minor bug fixes and updates to newer IntelliJ APIs.

Deprecation

• Support for IntelliJ platform 2024.3 is deprecated and will end with the launch of the EAP for IntelliJ platform 2026.3.
• Support for the OrchidE builder format V1 has ended.

OrchidE 2025.1.3 now supports ‘full qualified role name’ (FQRN) in OrchidE’s “New Ansible File” action and block “vars”.

Block vars

Code completion and the “Undefined variables” inspection now also detect block variables.

Changes

• New: Add support for IntelliJ platform version 2026.2 EAP.
• Bugfix: Ansible structure view doesn’t show inventory entries if an inventory file is in the projects root folder.
• Bugfix: Minor bugfixes.

Deprecation

• Support for IntelliJ platform 2024.3 is deprecated and will end with the launch of the EAP for IntelliJ version 2026.3.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2025.1.2 now supports ‘full qualified role name’ (FQRN) in OrchidE’s structure view for Ansible, inventory host entries with patterns, e.g., ‘server[1:2]’, and improves the ‘Find Usages’ action.

Full qualified role name support

FQRNs are now displayed in the structure view with their full names (namespace + name)

Support for inventory hostname patterns

Hostname patterns (e.g., server[1:2]) are now supported in code completion and navigation.

Improved ‘Find Usages’ action

The Find Usages action has been expanded for Jinja 2 references and variables. In roles, ‘Find Usages’ now finds definitions in role argument-specs and defaults files, as well as usage in Jinja 2 templates and declarations in inventory group/host variable files.

Changes

• New: A new inspection warns if a role is not being used by any playbook when “Use only current role for variable lookup” is enabled.
• Change: Support for new file / new Ansible file action has been improved in the Ansible structure view.
• Bugfix: In certain circumstances, the quick documentation did not show the attributes of a module’s return value.
• Bugfix: Host name definitions in YAML inventory files are ignored when the “Use only current role for variable lookup” option is active.
• Bugfix: Structure view: references are still shown as valid after a role folder has been deleted.
• Bugfix: Several role-related features, such as ‘goto role’ and code completion do not work for roles with only a tasks file.
• Bugfix: Custom schema validation for JSON files reports error when 0 and 1 are used as integer values (they were interpreted as boolean values).

Deprecation

• Support for IntelliJ platform 2024.2 is deprecated and will end with the launch of the EAP for IntelliJ version 2026.2.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2025.1.1 adds

• partial support for full qualified role names and Ansible Playbook projects, and
• improved quick documentation for return values.

Support for full qualified role names

Based on the playbook project structure proposed by Ansible Creator, this version provides initial support, for

• code completion in playbooks for FQRN,
• navigation in playbooks for FQRN,
• correct recognition of the ansible_collections path as a folder for roles, and
• for the role annotation in inventory files (code completion of the annotation, navigation to the role, code completion of the role variables, navigation to the role variables in argument_specs)

Currently, the following features are not supported for FQRN:
- Ansible Structure View
- Custom OrchidE ‘New File’ actions
- Detection of non-Ansible YAML files (can be configured via Ansible Folder Mapping)

Improved quick documentation for return values

The quick documentation has been expanded and now also displays information about sub options of return values.

Changes

• New quick documentation for return value sub-options.
• Basic new support for fully qualified role names (based on Ansible creator’s playbook project structure).
• New annotation showing an error when using Jinja2 template conditions (when, failed_when, etc.).
• Change: Quick documentation is now available for Jinja2 variables in the argument specifications or comments of the role defaults/vars variables.
• Change: Quick documentation is now available in the roles section of playbooks for vars keyword entries, using the description from argument specs.
• Change: Quick documentation is now available for Jinja2 variables referencing the register keyword of a module.
• Change: The quick documentation for keywords now includes information on the type and what it applies to.
• Bugfix: A parser error occurs when a collection uses an Ansible keyword as the name of its task.
• Bugfix: Various improvements have been made to the “Create Variable” quick fix when using undefined variables.
• Bugfix: Exception when using a Jinja2 template in conditions (when, failed_when, etc.).
• Bugfix: The Ansible structure project view doesn’t show folder names starting with a dot.
• Bugfix: If a key uses the flow style to define values, the Jinja curly braces will not be quoted during code completion.
• Bugfix: The include_tasks task would show an ‘unresolved include file’ error when Ansible-supported fact variables were used to resolve the default values.
• Bugfix: Top-level group variable files are not detected in the structure view.
• Bugfix: An exception occurs when trying to create a file with the ‘Ansible file’ action that already exists.
• Bugfix: NullPointerException when copying and pasting from a Jupyter playbook.
• Removed: Deprecated setting: File Type Patterns.

Deprecation

• Support for IntelliJ platform 2024.1 is deprecated and will end with the launch of the EAP for IntelliJ version 2026.1.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2025.1.0 brings contextual code completion in roles, various new “Go to Declaration” functions for the inventory and two new inspections.

Context-related code completion in roles

In roles, only variables are used for code completion, inlay display and the inspection “Undefined Variables” that

• are defined in the same role, and
• from the inventory when the role is referenced in the playbook hosts entry.

In the settings the previous behavior can be configured if necessary (Settings ➞ Editor ➞ OrchidE). This is recommended, for example, if variables from other roles are used.

Note: Role dependencies, defined in the meta file, are not supported by OrchidE.

New Go to Declarations

The annotations @role:: and @alias:: in inventory files now support the “Go to Declaration” action.

Using “Go to Declaration” on @role:: navigates to the corresponding tasks/main.yml file of the role. Using “Go to Declaration” on @alias:: navigates to the corresponding meta/argument_specs.yml file.

In inventory files, you can now navigate between the inventory group entries and to the group variables.

New Inspections

The inspection “Wrong usage of ‘item’” warns against the use of ‘item’ in loop if ‘loop_var’ is specified.

The inspection “Missing quote before Jinja template” checks whether Jinja templates {{ are quoted after a key or the start of a list.

Changes

• New code completion for alias annotation within inventory variable files.
• Code completion for role annotation within inventory variable files is now also available at the start of the line.
• Bugfix: Ansible module documentation could not be read if the description was available as a map (SAP collection).
• Bugfix: Files in the inventory folder host_vars are not recognized as inventory files.
• Bugfix: When opening Shell Jinja2 Ansible templates with the BashSupport Pro plugin, IntelliJ may freeze when saving.

Deprecation

• Support for IntelliJ platform 2024.1 is deprecated and will end with the launch of the EAP for IntelliJ version 2026.1.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2024.1.6 brings an improved Inspection ‘Missing File’.

In the copy and template task, missing files are now better recognized in the src attribute when a loop is used. Both the loop keyword with loop_control/loop_var and with_items with the placeholder item are supported.

Jinja templates in the file name are resolved as long as they are simple references to variables.

Changes

• New: Support for IntelliJ platform 2025.3 EAP.
• Change: Improved resolving of Jinja templates used in loop variable ‘item’.
• Change: Improved code completion in inventory files if an ‘alias annotation’ exists.
• Bugfix: Clear caches of inspection ‘Undefined Variable’ immediately when the variable name is renamed.
• Bugfix: When using the enter key for code completion of argument_spec variables, and the variable has a description, the indentation is incorrect.

Deprecation

• Support for IntelliJ platform 2023.3 is deprecated and will end with the launch of the EAP for IntelliJ version 2025.3.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2024.1.5 brings better support for the meta files ‘main’ and ‘argument_specs’, extended support for the src attribute of the copy task and various changes and bug fixes.

Meta/Argument_specs-Files

OrchidE now supports code completion and quick documentation for the meta and argument_specs files of an Ansible role and checks the syntax against the JSON schema. This function requires a current definition package of the OrchidE Builder, which contains extended JSON schema files (from Ansible 11.5 and 20250703).

Alternatively, IntelliJ’s built-in function for JSON schema can be used.

Differences between JSON schema of OrchidE Builder and IntelliJ:

• OrchidE automatically finds JSON schemas from the OrchidE Builder package. In IntelliJ, the schema must be configured manually for the meta files.
• Schemas from the OrchidE Builder package contain more detailed descriptions of the attributes.
• Newer schemas are available earlier with IntelliJ.
• With schemas from the OrchidE Builder package, some quick fixes are not available as long as OrchidE supports older IntelliJ versions. (<= IntelliJ version 2024.1)

Copy Task

OrchidE now supports code completion and verification for the ‘src’ attribute of the copy task identically to the template task. You can also navigate to the source file (go to declaration, Ctrl + B, ⌘ + B)

Changes

• New: New quick fix for module arguments with the wrong type.
• New: The quick documentation section “See Also” now supports external links.
• New: Support for code completion of variables defined by the vars keyword in the ‘include_tasks’ and ‘import_tasks’ tasks.
• Change: Jinja closing braces will now be added after typing second ‘{‘ immediately.
• Change: Jinja closing braces will now be added in Jinja templates files.
• Bugfix: Quick Documentation generates an error if no description is available for type.
• Bugfix: Action new Ansible file don’t use file extension from editor settings.

Deprecation

• Support for IntelliJ platform 2023.3 is deprecated and will end with the launch of the EAP for IntelliJ version 2025.3.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2024.1.4 brings minor bug fixes and support for IntelliJ platform EAP version 2025.2.

Changes

• Bugfix: Recognition of playbooks in root folders of roles.
• Bugfix: Exception occurred when a file or folder was deleted from within the Ansible structure project view.
• Bugfix: Exception when loading a collection with tasks for which no description is available (i.e. oracle.oci) from an OrchidE builder package V2.
• Bugfix: Minor fixes to error handling.

Deprecation

• Support for IntelliJ platform 2023.3 is deprecated and will end with the launch of the EAP for IntelliJ version 2025.3.
• Support for the OrchidE builder format V1 is deprecated.

OrchidE 2024.1.3 brings support for the OrchidE Builder format in version 2.

OrchidE Builder Format V2 is completely based on the output of ansible-doc, which makes it much easier to create your own package. With that, OrchidE provides improved quick documentation:

• Links to other modules
• ‘See also’ documentation is now included in quick documentation
• More detailed information in the deprecated section

Changes

• Change: OrchidE now recognizes playbooks in role folders.
• Bugfix: Fix java.lang.ArrayIndexOutOfBoundsException in OrchideInspectionUndefinedVariableFilterAndTestUtil.getAllBuiltInNames

Deprecation

• Support for IntelliJ platform 2023.2 is deprecated and will end with the launch of the EAP for IntelliJ version 2025.2.
• Support for the OrchidE builder format V1 is deprecated.