Sloane Hertel

@VannTen I've opened a pull request to backport this to stable-2.18, and this will also be included in 2.19.

`collection_plugins` -> `callback_plugins`

Fixed by #84488

The way to use alternative files is just above the section you quoted: > You can add other YAML files in some directories, but they won’t be used by default....

I noticed there are a couple out of date examples in docs/docsite/rst/playbook_guide/playbooks_async.rst too. Other than that, looks good to me. Could be fixed in another PR though.

I haven't tested this so perhaps there is a bug, but I'm wondering if this is just an awkward design. https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/rds/client/modify_db_cluster.html says: > DatabaseInsightsMode (string) – > Specifies the mode...

It looks like after the upgrade, libyaml isn't installed. Could you reinstall it and test again?

I bisected this to 27a56a34df7c7d879c2c0473aef5c58490024319. This wasn't a change I intended to make. I think we should restore the behavior, because `vars_prompt` and `vars_files` run regardless of `--start-at-task`. I'm not...

It was expected behavior as of 2.0: https://github.com/ansible/ansible/issues/15010. https://github.com/ansible/ansible/commit/27a56a34df7c7d879c2c0473aef5c58490024319 also broke the reproducer in that issue. Before: ```console PLAY [localhost] ************************************************************************************************************************************************ TASK [Gathering Facts] ****************************************************************************************************************************************** ok: [localhost] TASK [start here]...

PRs for auto-closed issues that were labeled with `waiting_on_contributor` are still welcome after the issue has been closed. Maybe ansibot could check for the `has_pr` label when checking if issues/PRs...