You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue with exporting the extra vars, it is changing the order of variables in structure to alphabetical. Moreover it sometimes do something like this (probably because of rearranging variables):
From what I've tested the culprit is the from_yaml | to_nice_yaml(indent=2)
Issue Type
Bug Report
Ansible, Collection, Controller details
Current versions
OS / ENVIRONMENT
RH9
Desired Behavior
Extra vars are properly exported.
Actual Behavior
Source extra vars:
_job_events_use_cases:
- name: unknown use casewhen:
matches:
- unknown use case - no match found with knowledge databaseactions:
- >- just an example
- name: '!well-known use case, no action needed'when:
matches:
- 'account_name .+ is not a valid account, cannot get SID'actions:
- >- another example
Exported extra_vars:
_job_events_use_cases:
- actions:
- >- just an examplename: unknown use casewhen:
matches:
- unknown use case - no match found with knowledge database
- actions:
- >- another examplename: '!well-known use case, no action needed'when:
matches:
- account_name .+ is not a valid account, cannot get SID
STEPS TO REPRODUCE
Create JT with long list of extra vars provided in source example
Export the JT with filetree_create
The text was updated successfully, but these errors were encountered:
Summary
Hey,
There is an issue with exporting the extra vars, it is changing the order of variables in structure to alphabetical. Moreover it sometimes do something like this (probably because of rearranging variables):
From what I've tested the culprit is the
from_yaml | to_nice_yaml(indent=2)
Issue Type
Ansible, Collection, Controller details
Current versions
OS / ENVIRONMENT
RH9
Desired Behavior
Extra vars are properly exported.
Actual Behavior
Source extra vars:
Exported extra_vars:
STEPS TO REPRODUCE
The text was updated successfully, but these errors were encountered: