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
However, no matter what configuration I try (inline, executable, or sourced from secret), I cannot get ansible in the provider to accept the inventory as a gcp plugin and run it correctly. It always gives the error
[WARNING]: * Failed to parse
/ansibleDir/733c9dbc-1b0b-4b44-ae41-e935f962b9a9/hosts with yaml plugin: Plugin
configuration YAML file, not YAML inventory
Turns out this is because ansible inventory plugins enforce a fixed structure on inventory filenames, and each plugin defines what the inventory files must be named (on disk) for the plugin to accept them.
For example the docs in gcp state
Uses a YAML configuration file that ends with gcp_compute.(yml|yaml) or gcp.(yml|yaml).
What problem are you facing?
I am attempting to use the ansible provider in crossplane as an execution engine for an existing ansible setup. This setup makes use of the gcp_compute ansible plugin https://docs.ansible.com/ansible/latest/collections/google/cloud/gcp_compute_inventory.html
However, no matter what configuration I try (inline, executable, or sourced from secret), I cannot get ansible in the provider to accept the inventory as a gcp plugin and run it correctly. It always gives the error
Turns out this is because ansible inventory plugins enforce a fixed structure on inventory filenames, and each plugin defines what the inventory files must be named (on disk) for the plugin to accept them.
For example the docs in gcp state
How could Crossplane help solve your problem?
Expand the
AnsibleRun
CRD to supportinventoryFilename
either oninlineInventory
or all inventory sources. Instead of hardcodinghosts
at https://github.com/crossplane-contrib/provider-ansible/blob/main/pkg/runnerutil/runnerutil.go#L30If we can specify the filename the provider loads the
inlineInventory
into, we should be able to leverage any and all inventory pluginsThe text was updated successfully, but these errors were encountered: