I am experimenting with Ansible integration for my Aria Automation environment using a basic control server. I've set up the integration and added an Ansible block to one of my cloud templates, and the Aria Automation appliance successfully communicates with the control server, but the tasks executed on the control server during deployment mangle my inventory file and prevent playbooks from running. The inventory is in YAML format, but the task appends INI-style lines to it for the newly-deployed host, causing future playbook runs to fail as the inventory format is invalid.
Watching ansible debug log output on the control server while I request a VM from my Aria Automation catalog, I see ansible parse my inventory with the yaml plugin, but it then runs a task using a bundle containing the ini_file module that appears to have been sent from the Aria Automation appliance, which adds lines to the inventory as if it were an INI. Aria Automation reports the deployments as a success, but nothing is actually accomplished on the Ansible side due to the inventory errors.
Is there something extra I need to do to make Aria Automation generate the right user_defined_script content for a YAML inventory? I've been all over the official documentation for this and a few blog posts, but none of them go into any detail on how the scripts that run on the control server during deployment are generated, what kind of communication takes place, or where adjustments can be made.