The following commit e20ad3f91e621b12dabcd8291aa674e92811f329 introduced an option to supply custom Ansible variable for plugins instead of using Infrared's generated variables.
When using custom Ansible variables, they do not get resolved according to ComplexType's type.
Using the following plugin-spec:
---
config:
plugin_type: other
subparsers:
foo-plugin:
description: foo
include_groups: ["Ansible options", "Inventory", "Common options", "Answers file"]
groups:
- title: Foo
options:
foo:
type: FileValue
help: 'File to be fetched from URL'
required: yes
ansible_variable: my_var
Description
The following commit e20ad3f91e621b12dabcd8291aa674e92811f329 introduced an option to supply custom Ansible variable for plugins instead of using Infrared's generated variables.
When using custom Ansible variables, they do not get resolved according to ComplexType's type.
Using the following
plugin-spec
:Current behaviour
Executing infrared command
infrared foo-plugin --foo tox.ini
:This thus not resolve the file's absolute path as per the documentation.
Expected behaviour
Executing infrared command
infrared foo-plugin --foo tox.ini
: