ansible/test/integration/targets/module_precedence/modules_test_role_ext.yml

- hosts: testhost
  gather_facts: no
  roles:
    - foo
  tasks:
  - name: Use ping from role
    ping:
    register: result

  - name: Use  from role
    a:
    register: a_res

  - assert:
      that:
        - '"location" in result'
        - 'result["location"] == "role: foo"'
        - 'a_res["location"] == "role: foo, a.py"'
Filter BLACKLIST_EXTS in PluginLoader (#69029) Change: Rather than hardcoding .pyo and .pyc, filter on all BLACKLIST_EXTS in the non-legacy logic of PluginLoader (_find_fq_plugin). The two harcoded extensions are part of BLACKLIST_EXTS already and this simply adds the rest of the blacklisted extensions to the check. In addition, check .endswith() instead of an exact match of the suffix, like everywhere else that uses BLACKLIST_EXTS. This allows for blacklisting, for example, emacs's backup files which can appear after any extension, leading to things like `foo.py~`. Test Plan: Ran `ansible-playbook` against a collection where a `foo.py~` module was getting executed instead of `foo.py` which also appeared in the same directory. `foo.py~` is no longer executed. Tickets: Fixes #22268 Refs #27235 Signed-off-by: Rick Elrod <rick@elrod.me> 5 years ago			`- hosts: testhost`
			`gather_facts: no`
			`roles:`
			`- foo`
			`tasks:`
			`- name: Use ping from role`
			`ping:`
			`register: result`

			`- name: Use from role`
			`a:`
			`register: a_res`

			`- assert:`
			`that:`
			`- '"location" in result'`
			`- 'result["location"] == "role: foo"'`
			`- 'a_res["location"] == "role: foo, a.py"'`