Jad Seifeddine

@VF-mbrauer can you share your execution-environment.yml Have you done any troubleshooting? Tried using a different version ? May be irrelevant but I run ansible from the host machine, as well...

Solved... sorry to trouble you... For anyone else with similar desires please read, save you some time: https://forum.ansible.com/t/ansible-inventory-e-extra-vars/3808 Cheers

Don't know if it is relevant to this issue, We have a persistent issue with wait_for_connection always failing due to some cached route/flow black hole... But the issue is outside...

> @j-oss2023 If the issue is the Python interpreter changing mid play, you could fix it by running a `- meta: clear_facts` task before calling `wait_for_connection` (and then run `gather_facts`...

i've hacked it up and made it work now, built my own docker image, ./pkg/probe/system_interface.go ```go package probe import ( "log" "github.com/bluecmd/fortigate_exporter/pkg/http" "github.com/prometheus/client_golang/prometheus" ) import "strconv" func probeSystemInterface(c http.FortiHTTP, meta...

> Hello, > > It would be very nice if you can submit a PR instead so we all can benefit from it :) I've not submitted a PR before...

There you go @lazyb0nes #279 PR submitted... Go easy on me, first time :D

Please also see: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/constructed_inventory.html#parameter-use_extra_vars

Thanks @fosterseth and @AlanCoding for your response... Is there any way for me to modify the cloned repo to add this in a quick fix ? Like the invocation of...

> Thanks @fosterseth and @AlanCoding for your response... > > Is there any way for me to modify the cloned repo to add this in a quick fix ? Like...