flowerysong

> IMHO the validation task should not run if nothing is targeted by a tag, just like facts are not gathered if nothing is targeted by a tag. They are...

> I understand there are technical differences but if we are strictly talking from a user experience point of view, then it feels strange that the argument validation occurs when...

Not directly relevant to your issue, but I did want to flag up for you that the modern way to provide documentation for non-Python modules is in a YAML sidecar...

I still don't think this is the correct thing to do; as outlined in https://github.com/ansible/ansible/issues/82670#issuecomment-1939219515 this would mean that validation could be skipped even when tasks from the role run.

`wait_for_connection` does contain an attempt to make interpreter discovery retry (https://github.com/ansible/ansible/blob/bd6feeb6e7b334d5da572cbb5add7594be7fc61e/lib/ansible/plugins/action/wait_for_connection.py#L82-L84) but I'm not sure it's sufficient.

Propagating the undefined value "upward" to make the whole dictionary undefined is the intended behaviour, not a bug. See https://docs.ansible.com/ansible-core/devel/porting_guides/porting_guide_core_2.14.html#playbook

Works for me. If I copy the example task and remove the `until`, it retries five times and then gives up. ``` - hosts: localhost gather_facts: false tasks: - name:...

LGTM. I've integrated this and the other outstanding PRs that looked reasonable into the `main` branch at https://github.com/flowerysong/OpenARC. I'm on vacation for the rest of the week so I don't...

The actual criterion for removing this is support for ansible-playbook < 2.11; the release of 2.15 will not require you to remove this setting if you're still supporting ancient versions....

`the ‘smart’ option for setting a connection plugin is being removed as its main purpose (choosing between ssh and paramiko) is now irrelevant.` is part of the "Deprecated Features" portion...